The network
This site is one of a network of publishing sites under sgit.ai, each owning a domain and linking rather than duplicating. This site owns the subscription standard, the register, and the UK levers; it borrows vocabulary and infrastructure from its siblings rather than rebuilding them.
Who owns what
| Site | Owns | How this site uses it |
|---|---|---|
| sgit.ai | The parent project: the vault layer, the CLI, the platform documentation. | The substrate for the vault architecture the whole workflows page runs on. |
| risks.sgit.ai | Risk: registers, scoring, evidence. | The vocabulary this register's record-only design borrows — a register that scores nothing is still a register. |
| standards.sgit.ai | Standards and the grounding vocabulary; instruments as graphs. | The law pages link its method (dated provisions, “derived not canonical”) rather than rebuilding it. |
| nfrs.sgit.ai | The dated-page and staleness discipline, from the inside. | This site is the sharpest test case for that discipline: a stale legal page is a false memory that gets a reader corrected by a trader. |
| open-source.sgit.ai | The standard-as-adoptable-artefact argument; the CC BY rationale. | The reasoning behind standard-before-law sequencing. |
| llms.sgit.ai | The LLM boundary and provenance; agentic workflow conventions. | The conventions the parsers are expected to follow. |
| coding.sgit.ai | Coding conventions and the formatting discipline. | Followed by this site's build tooling. |
The pattern this site's split follows
risks.sgit.ai and its commercial counterpart riskmandate.ai split content out of a commercial site over time. This site starts the other way round: everything unified now, with /service/ designed as the one directory that would split off to its own commercial property later, if a business partner emerges. Read the split design →
What being part of a network costs
Every entry above is a link this site depends on and does not control. A link to a sibling that has not yet shipped a page this site references is a fact about the network's build order, not a defect in this site — and it is checked, not assumed: admin/build/check_siblings.py reports on it as a build-time tool rather than a release gate, because a sibling's outage should not turn this repository's CI red for a reason nobody here can fix.