sagitta.systems went online as the public record of the network: a directory of the operating systems, a newsroom, press and journalist resources, a careers and contributor centre, and a public roadmap.
The hub exists because the network had a structural problem that no individual product surface could solve. Sagitta's systems run on their own subdomains, each with its own audience and its own reason to exist, and a reader arriving at any one of them had no way to see how it related to the others — or to establish who was behind it, what state it was actually in, or whether the claims on it could be checked.
So the hub does four things the product surfaces deliberately do not. It explains: each system has a record stating what it is, who it is for, and what is usable today. It connects: the three families — continuity and defense, allocation and agent intelligence, capital infrastructure — are published as a structure rather than left to be inferred from a list of names. It documents: the whitepaper, the architecture, the allocation methodology, and the machine-readable surfaces are indexed in one place. And it routes: every record ends by handing the reader to the surface that can actually serve them.
The operating principle is that every claim carries the evidence behind it. Operating states are recorded with the date they were checked and the surface they were checked against. Figures carry their metric, scope, and source. Where something is not known — a date a source never published, a page count nobody read — the field is left empty rather than filled by inference, and the record says so.
Operating products continue to run on their own subdomains. This hub is the layer that explains, connects, documents, and routes across them, and it is the canonical location for the network's own record of itself.
