The whitepaper sets out an autonomous investment management system that prioritises capital safety over yield optimisation, enforcing fiduciary responsibility through architecture rather than operator discretion.
It documents the Vault for custody and accounting, the Treasury for liquidity and settlement, the Reserve as a gold-backed insurance layer, Escrow as the interface to external allocation venues, the Autonomous Allocation Agent for quantitative recommendations, and the Continuity Engine for survival and recovery.
The organising commitment is the ordering of those priorities. Most capital systems are designed to maximise return subject to surviving; this one is designed to survive subject to returning, and the difference shows up in the architecture rather than in the marketing. The Reserve exists outside the allocation path. Continuity is a component of the protocol rather than a procedure invoked after something goes wrong. The allocation agent produces recommendations inside a policy envelope it cannot exceed, and its reasoning is preserved with the decision.
The document also carries the doctrine, which is the part that generalises past this protocol: failure states should be named, bounded, and given revival paths before they occur, and a system should be judged on what it does when protection is insufficient rather than on how unlikely it claims that is.
This is the protocol's design, published in full. It is not a deployment record — Sagitta Protocol remains in Public Test on Moonbase Alpha Testnet and Arc Testnet, and the whitepaper describes the architecture rather than a shipped mainnet system.
It is published and maintained externally on GitBook. No version number or publication date is stated on the document, so none is recorded here.
The complete work lives elsewhere
This page is the canonical Sagitta record. The full publication is hosted on its own surface and opens in a new tab.
Read the whitepaper (opens in a new tab)