Purpose, decision architecture, human architecture — the shape of the transformed organization. Read, debated, adopted.
Runs as an engineering framework
GOVERN / ASSURE · Safe Autonomy · Four Pillars
A control plane, an identity constraint, four services with SLAs — systems that either run or don't. Built, deployed, measured.
↑ the same framework · two readings ↑
01 · The discipline
The agent proposes. The platform permits.
This is the dimension everyone overfunds and least understands: buy the model, assume the platform will hold, discover at machine speed that it doesn't.
The discipline isn't making the agent powerful. It's building the boundary the agent can't cross. Every action it wants is a proposal — something else decides whether it is permitted, writes it, logs it, makes it reversible. Or it never happens.
Built right, the platform isn't the centerpiece. It's the floor the other two dimensions stand on.
The line
Propose vs. permit
The agent never touches the source. It asks; the boundary decides. The two are never the same thing.
The record
Nothing happens silently
Identity on every action, a correlation ID through every change. What passed the boundary is always answerable-for.
The floor
Immutable underneath
Once a decision or a payment is recorded, no one — not an agent, not an admin, not you — can quietly change it.
02 · The framework compiles
Every governance term has a technical address.
Take each construct and ask what has to be running for it to be true — not adopted, running, under load. Left column is the spec; right is the implementation contract.
The ExO 3.0 construct
The property it compiles to
The governance control plane
GOVERN / ASSURE · across the Intelligence Stack
→ compiles to
A logging-and-interdiction plane that is never off
"Never off" is an availability guarantee, not a policy. Every decision logged, every guardrail evaluated, the kill switch live — at machine speed under production load. A plane that pauses under pressure is one the framework doesn't have.
Safe Autonomy · the Fiduciary Wedge
SHAPE · the accountable-human chain
→ compiles to
Identity bound to every action; unownable actions refused
"Every decision chains to a named human" is a referential-integrity constraint. Anything that can't resolve to an accountable principal is rejected at the boundary, not logged after the fact. No examiner hears "the algorithm did it" — the system could not have executed it.
The Four Pillars
the production test · real or decorative
→ compiles to
Four running services, not four intentions
Trusted evals, searchable logs, granular rollback, a human-review queue — each a service with an SLA, deployed and answering or not. Score the four and governance is measured, not asserted. Most organizations pass one. That gap is the size of this dimension.
A framework you can adopt is a philosophy. A framework that compiles to systems is a specification.
03 · The machine inside the framework
This is what the spec looks like running.
Those three constructs are one enforcement point seen from three angles. A proposal arrives, the interdiction point checks authority and integrity, and it is permitted and written, or refused. No product names appear because none are required — only the properties.
The agent
Proposes
"here is what I'd do"
move money · change a rule
✕can't be owned → refused at stage 1
The interdiction point · enforced
Stage 1 · IdentitySafe Autonomy
Who is accountable?
bind the action to a named human — or refuse it here
Stage 2 · Policy + integrityGovern / Assure
Is it permitted?
evaluate guardrails, at speed, under load — never off
one point · three stages · each a framework construct, running
The source
System of record
the source you own
written · logged reversible · owned
once recorded, no one quietly changes it
ExO 3.0's control plane, drawn as the running mechanism it specifies
The same interdiction point pays off before any agent arrives: knowing what a change touches before it lands is what lets you change the system safely at all. The Remediation Gap makes that case in full.
To be precise about what this is
This dimension is not about buying the most capable model — it's about the boundary beneath it. A more capable agent makes that boundary more necessary, not less. It is built beside the systems that already run the business, not by forking them: the source stays owned, the platform stays the source of truth.
This axis has a name
Reggie Britt
Technology · the enterprise CTO seat
$1B+CTO · regulated consumer finance
3software companies founded
40years · high-volume regulated systems
Forty years designing and operating the systems where the distance between an experiment and production is measured in real consequence — the judgment that comes from having been the person who had to answer for whether the platform held.
Can your systems actually carry an agent — or only demo one?
The HOT Readiness Scan reads your people, your organization, and your technology — each its own score against published anchors. Five minutes, no email required, the result is yours to keep.
The ExO 3.0 framework — MTP, DRIVE, SHAPE, the Intelligence Stack, and the REWRITE playbook — is the work of
Salim Ismail and contributors. OpenExO · The Organizational Singularity ↗