Databricks published an architecture manifesto for the agentic era.
It is a serious document. A dozen of its executives argue one case: intelligence lives in the context layer, not the model; governance belongs inside the system that produces quality, not beside it; unify rather than stitch point solutions; do not trade software sprawl for agent sprawl. Their Chief AI Officer sets the security standard in a single line — an organization that cannot trace which data the AI used to produce an answer is, in her words, “not secure” [1].
Every one of those claims is a write-path claim. Build it in. Govern where the state is written. Keep the trace.
In the same week, the same company shipped Omnigent: a meta-harness that wraps Claude Code, Codex, and the rest as black boxes, governs the seam between them, and treats the harness as an interchangeable field [2] [3].
The two columns
| The eBook preaches the write-path gospel |
Omnigent ships the read-path heresy |
|---|---|
| Build intelligence into the system | A layer in front of the harnesses |
| Govern inside the system that produces quality | Govern the seam; harnesses stay black boxes |
| Trace which model used which data | Swap model and harness mid-loop; provenance fragments |
| Unify — do not stitch point solutions | Federate and multiplex many harnesses |
| Do not create agent sprawl | Sprawl, with a ring on top |
| Governance is context and quality, inside | Governance is a risk score, outside [4] |
Nothing in that table is inference. The left column is the manifesto’s own argument. The right column is Omnigent’s own documentation — the policy event that carries a tool name, its arguments, a token bill and a counter, and nothing of the reasoning that produced them [3] [6].
Not hypocrisy — two governance models
Two documents, two layers. The eBook describes the data layer, where Databricks owns the substrate — and there the architecture is coherent, and it is the write path. Omnigent describes the harness layer, where the providers own the substrate — and there it inverts.
The honest reading is not that anyone contradicted themselves. It is that two different architectures are being described, and only one of them is available to a company standing where Databricks now stands.
Governance intrinsic: the control lives inside the system that produces the decision, with the trace attached. That is what the manifesto argues for, and it is correct.
Governance above the runtimes: the control sits over a fleet of opaque executors and gates what crosses the boundary. That is what Omnigent implements, and it is what remains possible when the layer beneath you belongs to someone else.
Where a company owns the substrate, it preaches the gospel. Where it has been displaced, it ships the ring.
A vendor’s manifesto tells you what it believes. Its product tells you what it can still reach. When those diverge inside one company in one week, the divergence is not a communications failure — it is a map of where the substrate has already moved.
The compression is not a forecast. It is legible in the gap between what a displaced incumbent knows to be true and what it is able to sell.
The write path is not a market position. It is where state is written, and it is the only place assurance can be authored [5]. The manifesto knows this. The product cannot act on it.
