Why five
Why Build, Run, Observe, Control, Secure, and no other set. What was considered and rejected.
Frameworks earn their keep by being the right size. Three parts and you are hiding the hard bits inside one of them. Nine parts and nobody remembers it, which means nobody uses it in the meeting where it would have helped.
Five is not a design choice made for symmetry. It is where the sentence came out.
The sentence
The framework started as a question from an engineering leader at a healthtech company, after several weeks of evaluating the AI tooling market:
I need somewhere to build it, somewhere to run it, a way to see what it’s doing, and ensure it doesn’t go off the rails.
That is Build, Run, Observe, Control, in order, from someone who had no framework and no interest in one. He was describing the shape of the hole.
Secure is the fifth because the next conversation is always with the CISO, the compliance officer, or the regulated buyer, and it is not a subset of the other four. “It doesn’t go off the rails” is an operational statement about your own system. “Prove it, to an auditor, for a system that generates its own text” is a different job with different artifacts and a different owner.
The test each letter has to pass
A letter earns its place if all four of these hold.
- Someone owns it, and it is not the same someone. Build belongs to platform or developer experience. Run belongs to infrastructure. Observe belongs to whoever carries the pager. Control belongs to architecture and identity. Secure belongs to security, compliance, and finance. Five letters, five different budget lines and five different rooms.
- Skipping it produces a distinct, observable failure. Not a worse version of another letter’s failure. The failure-mode library is the evidence for this one.
- It has a mature adjacent discipline to borrow from. None of these are new. Each letter has decades of prior art that transfers with modest amendment. See adjacent practices.
- You can be at zero on it while being strong elsewhere. If a letter always moves with another letter, it is not a letter, it is a facet.
What was considered and rejected
Govern as a separate letter. Governance without enforcement is a document. The useful version of governance is policy encoded in the place where the action happens, which lands inside Secure and Control rather than floating above them. A sixth letter here would have created a home for exactly the artifact the framework is arguing against.
Data as a separate letter. Tempting, because data is where most AI programs actually stall. It failed test one: data access for builders is a Build problem, data at rest and in motion is a Run problem, data retention is a Control problem, and data residency is a Secure problem. Pulling it out creates a letter that nobody can own end to end and leaves four letters with holes where the data used to be.
Cost as a separate letter. Inference cost is genuinely different from compute cost: more elastic, harder to forecast, and easy to hide in a single corporate card. But cost control without attribution is impossible, attribution requires per-app and per-team telemetry, and that telemetry is Observe. The decision to cut off a team is Secure. The letter would have been a reporting layer over two other letters.
Evaluate, or Measure, as a separate letter. Evals are how you know Observe is telling you something true. They belong to Observe the way tests belong to Build.
Merging Control into Run. This is the most common objection, usually from people with a strong platform team, and it is wrong for a specific reason: Run answers “is it up”, Control answers “can I change it, and can I change it back”. Plenty of organizations have an excellent Run story and no ability to move a workload between model providers without a code change. That is a real gap and it needs a name.
Why the order
The letters are in the order work happens. Someone builds something, it runs, you watch it, you steer it, you answer for it. That order is also the order things get skipped: almost every organization starts at Build, most get to Run, fewer reach Observe, and Secure is usually a retrofit after an incident or an audit.
The order is not a maturity model. You do not finish Build and move on. Each letter hands off to the next and the last hands back to the first: what you learn in Secure changes what you are willing to let people Build.