Architecture

Why the fabric exists, who owns which box, then the internals. Component pages are the deep end.

The story first: how it hangs together. What actually runs today: autonomy.

Where to start

Page	For	In one line
The idea	Anyone	One door, controls once, intelligence in domains
Operating model	Owners and reviewers	Who publishes, who approves, who runs it
Technical design	Engineers	One decide contract, two AFD fleets, three principals

Components

One page per deployable box: deployment, APIs, data, sequences, failure. These pages assume you already have the story.

Component	Box	Job in one line
Agent Front Door	Chat AFD + API AFD	Only way in. Entitle, freeze, start. Two fleets, one contract.
Agent Plane	ACP + Agent Data Plane	Catalogue and classify. Does not pin or start Runtime.
Agent Runtime	AR + Shared calls	Pin, hydrate, run the graph, autonomy modes 0–3.
Agent Audit	AADP + AACP	Producers emit async. Append-only evidence chain.
Agent Capability Plane	Registry (with Agent Plane)	Publishers append id@version. Runtime hydrates at pin.

Locked fabric rules

1. Four jobs. Front Door entitles, pins, starts. Data Plane classifies. Control Plane is control and audit. Runtime runs.
2. Two Front Door fleets, one contract. Separate process at production scale. Runtime return is not a third door.
3. Jobs name route_id. Skip classifier and clarify. Do not skip entitle and record.
4. Generic chat still classifies. Hints are eligible and chat-visible.
5. Only route starts Runtime. Clarify and abstain never pin.
6. One Agent Plane per trust domain. Not one mega-agent.
7. Three principals. User ≠ agent ≠ Runtime workload.
8. Capabilities are references. Runtime hydrates the whole pinned manifest before the model.