The fabric
Separate products.
One contract between them.
You do not buy a fabric. You have one already — the moment AI parts are acting across your enterprise, your products and your environment. What we sell are the components that make it governable: each a product in its own right, each usable without the others, and each built so that what one promises the next is built to receive.
The shape of it
Operations Center is how a changed rule reaches every runtime below — on one machine or an estate.
Beneath every step: RFS and NME hold state and meaning, and MAE on the Unified Calculus supplies the rules and their proofs.
The three seams where the fabric enforces today
Most of this market governs one place.
A guardrail vendor checks the model's output. A gateway checks the tool call. An identity vendor checks who the agent is. Each is a patch over one seam of a fabric nobody is describing as a whole.
At the model's output
Deterministic predicates check what the model said. No model anywhere in the decision path.
At the action boundary
Every consequential tool call arrives here first, and a refusal means it never executes.
Inside the software you ship
Enforcement running on your customer's infrastructure — the seam no cloud console can reach, because it is not their estate.
What each one is for
Eight components, and what each is for.
The action gate
The Universal Control Plane. Every consequential tool call arrives here first, the rules answer most of them, a person answers the exceptions, and a hash-chained receipt records what happened.
Access is not authority →Governed inference
Model output is checked by deterministic predicates — same input, same verdict, no model judging a model — and violations drive a repair loop rather than only a refusal.
We don't run your model →The engine that makes the rules
Turns a stated rule into proved mathematics and seals it into an installable package with its evidence inside.
A rule is an opinion →Inside the software you ship
A governed runtime that runs inside the software you ship. You tell us what has to be governed, the engine proves the rule, the rule is sealed into the runtime, and your build includes it at the seam you declare. It stays connected to Operations Center, so when the rule changes you do not ship a new version of your product. Released, signed, and registered in the control plane.
The seam no console can reach →A governor for a transformer
Clips onto a transformer and holds its internal state inside a proved boundary at inference time. Eleven kernel-checked Lean theorems and a working edge runtime with zero measured drift on the processor.
What was asked, and the plan
MAIA runs today as a single sealed file of eight megabytes, offline, with no network capability anywhere in its decision path, returning a hash-bound decision artifact and a receipt. CAIO plans and is structurally forbidden from executing — its schema rejects any plan carrying a result.
Memory and meaning
The memory substrate and the meaning encoder beneath it, including a capacity proof that refuses to compile an operating point outside its own law.
How a changed rule reaches every runtime
Not a console. The delivery mechanism a re-proved rule travels on — to every runtime holding the old one, including runtimes embedded in software you have already shipped.
The personal layer
The assistant a person actually talks to, with the fabric underneath it.
Operations Center
Not a console. The way a changed rule reaches every runtime.
It carries the rule, not the dashboard
When a clause moves and the engine re-proves the rule, this is what delivers the new sealed artifact to every runtime holding the old one. Nothing is retrained and nothing is redeployed.
It reaches the software you sell
A governed runtime embedded inside your product, shipped to your customers, stays connected to it. That is the only reason a rule inside somebody else's infrastructure can change at all.
It runs for one person, or an estate
The same plane an enterprise uses can be run by an individual on their own machine. A cloud vendor's console lives in their tenancy; none has a single-person mode, because none can.
Start at one seam
Start at one seam. There is no platform decision to make.
Every component is a product in its own right and works without the others. Take the action gate on your coding agents and leave everything else alone; if it earns the next seam, take that one. We think that is the honest way to sell something this early, and it is also the only way we would buy it.