The diagram traces capital through the protocol: deposits into the Vault, liquidity managed by the Treasury, the gold-backed Reserve, Escrow as the interface to external venues, and the two intelligence systems — the Autonomous Allocation Agent and the Sagitta Continuity Engine — governing allocation and continuity.
What it is useful for is seeing the boundaries. A component list tells a reader which parts exist; the diagram shows where capital crosses from one authority domain into another, which is where the design decisions actually live. Capital entering the Vault is under one set of rules. Capital moving through Escrow to an external venue has left the protocol's direct control and is under another. The Reserve sits outside the allocation path entirely, because an insurance layer that can be allocated from is not an insurance layer.
The two intelligence systems are drawn as components rather than as services attached to the outside. That is deliberate and it is the diagram's main claim: allocation decisions and continuity decisions are made inside the protocol's own boundary, not delegated to something the protocol calls out to and hopes is available. A continuity engine reachable only by a working system is not a continuity engine.
This is an architecture document. It shows how capital is designed to move, not a deployment: Sagitta Protocol remains in Public Test on Moonbase Alpha Testnet and Arc Testnet.
The diagram is cleared for press use and is available at full resolution in the media library.
Open the full asset
This page is the canonical Sagitta record. The asset itself opens directly.
Open the full diagram