AI controls architecture

Primitives are not architecture. The design problem is knowing which controls apply, how they compose, and whether they keep working.

Cell biology as a design constraint for agent governance: scoped permission, compartmentalisation, lifecycle.

Why the unsolved AI risk is not a missing technique but a missing institutional accountability layer.

The useful unit in agent systems is not a better instruction. It is a tested capability package: judgment, code, checks, routing, and boundaries.

Model revenue is not customer return. The economic and risk unit is the harness that turns model output into accountable work.

Once model companies supply the generic agent harness, the valuable work moves into workflow design, human intervention, domain data, and the definition of good work.

Enterprise AI stops being a chatbot when the operating procedure becomes the thing the system can execute, inspect, and improve.

Long-running agents are not defined by the model call. They are defined by the state, rules, tools, failures, and corrections that survive it.

Ken Griffin watched PhD-level finance work compress from months to days. The interesting question is whether bank AI controls are designed for the layer where the work now lives.

If a product wants agents as real users, first-run setup has to be an executable workflow, not a human signup ceremony wrapped in documentation.

Coding agents move the bottleneck from implementation to shared intent.