Engineering organizations for the AI era
Org charts are runtime systems. The AI era exposes which structures were load-bearing and which were ceremony.
This essay is a placeholder. The shape is right — eyebrow, serif headline, lede, prose body, room for code, pull-quotes, and an in-page table of contents on wide screens — but the words below are scaffolding, replaceable paragraph by paragraph as the position stabilises.
The argument
Most of what passes for AI strategy is content marketing wearing a roadmap. The actual question is structural: what shape of organisation produces decisions an AI system can usefully participate in, and which shape produces noise at higher throughput.
The interesting unit is not the prompt or the model. It is the seam between the team and the contract.
What this implies
If the seam is well-defined — the Agent Contract, the Inspector Pipeline, the Capability Maturity Ladder — then adoption becomes a matter of running the loop. If the seam is undefined, no amount of model improvement closes the gap.
// promotion is mechanical inspector.observe(cell.traces) .detect(patterns) .propose(capabilityChange) .review(governance) .promote(L1 → L2 → L3)
What replaces this
The full essay will replace this scaffold. Until then, the structure shows the intended shape: short sections, named claims, and code or contracts where prose would only handwave.