Site architecture, and the split designed in from day one
Summary
The document this site's structure is built from directly. It names the decision the whole architecture serves: everything ships unified now, and the commercial service splits out later to its own property if a partner emerges — the riskmandate.ai / risks.sgit.ai pattern, run in the other direction. Three mechanisms make that cheap: the register data lives in a vault the site only renders, so re-pointing moves the register without touching an entry; the service pages live entirely under /service/, with nothing else linking into their internals; and the licence boundary is drawn now, CC BY everywhere except that a partner's branding and pricing stay thin. It then lists the site page by page, which this release follows directly.
Key concepts
Key ideas
- Design for the split now and it is a DNS change; ignore it and it is a migration.
- The register vault re-pointing structurally answers the founder-led-register criticism: the data was never coupled to the founder's domain.
- /workflows/ doubles as the sgit showcase and should be linked from sgit.ai.
- The law pages are the ones with a known expiry date.
On this site
Followed page by page. /service/ is thin at launch, exactly as specified, and every other page ships in this release.