How we think.
The vision is the why; this is the how — the doctrines the engine refuses to break, stated as opinions with reasons attached. Each one exists because the opposite cost something real.
Doctrine 01
Nothing is claimed before it exists.
Marketing writes checks that engineering cashes; when they drift, trust is the casualty. So the site carries a status page stamped with the engine commit it was generated from, the threat model grades its own containment layers and names its gaps, and a claim without a pinned test is a bug — whoever wrote it. Honesty here is not a value statement; it is a build constraint, the same way “unknown keys are loud errors” is.
Doctrine 02
We are our own reference customer.
The workflows the site advertises are the workflows the maintainer runs. The registry’s own tasks are dev-crew examples; the review loops that guard the engine are engine workflows under the same gate. If a governed step is harder to run than an ungoverned one, the maintainer feels it first — that is the point. Software that sells discipline it does not apply to itself is a brochure.
Doctrine 03
Compose, don't reinvent.
The gateway is someone else’s good work, composed wire-only under Apache-2.0 — not rebuilt, not forked, not vendored. The same rule decided the bus, the schemas, and the CI ladder: adopt the boring, proven piece and spend the invention budget where nothing proven exists — the governance core. Not-invented-here is a tax on maintainers; this project is one maintainer.
Doctrine 04
Contracts before code.
Every wire payload lands with its schema in the same change; unknown keys are loud errors, never warnings; two services agree by schema or the build is red. The discipline feels heavy on day one and cheap by month two — drift is where systems go to become unmaintainable, and a schema is drift’s earliest alarm. Code is the easy part; agreeing on what a message means is the work.
Doctrine 05
Small judgment, big work.
Gate a fleet on human attention and it waits on you; gate it on a model that can talk and it can talk its way past a rule. So the gate is a 421M-parameter non-generative model that answers typed questions and literally cannot leave the schema — reflexes, not a brain. The large models do the work; the small one does the triage, fails closed when it is down, and every decision is labelled against outcomes so the next gate is trained on evidence, not vibes.
Doctrine 06
One orchestrator per flow.
When two systems orchestrate the same flow, you get two sources of truth for state, retries, and audit — which is how incidents are born. So the boundary with integration engines is written down, not improvised: deterministic plumbing stays with the operator’s engine of choice; anything that needs judgment, a human door, or a log of record belongs here. The test is one sentence — if any step needs judgment or a HITL, the flow belongs to AiOverload — and it cuts both ways.