04 — Site Architecture

The house pattern

Copy pki.sgit.ai; add /llms-full.txt. This site's character: the hub — it owns the topic map and the homeless disciplines, and links out relentlessly. Resist the pull to duplicate; the deconflict table in 01__ is the contract.

Page by page

/ — NFRs expanded in sentence one; the villagers definition as the epigraph ("version control, reliability, resilience, security, backups, consistency, explainability, and documentation"); the hub claim; and the scorecard teaser.

/map/ — 01__ in full. Build first. One page an agent reads to know where everything lives. Machine-readable twin required.

/memory/ — 02__. The thesis page — and propose it to sgit.ai for the hub as well.

/testing/ · /ci/ · /documentation/ · /budgets/ · /pm/ · /resilience/ · /ifd/ — the owned disciplines from 03__, one page each, each closing with its counter-evidence and a link to the sibling pack holding the measurements.

/scorecard/ — the estate measured against its own eight-NFR list (00__ §4). Links each cell to evidence. Regenerate per release.

/backups/ — the honest stub: the one NFR on the list with no doctrine. State it, date it, and let the stub shame the gap closed.

/shipped/ — what this site asserts vs what the estate demonstrably does; the generate-or-date rule for every number.

/network/ · /admin/ — house pattern; build order published unresolved.

Generated, not written

The topic densities · the scorecard · every measurement quoted from sibling packs (link, do not restate) · the map's link targets. This site quotes more numbers than any other in the network — it has the most to lose from drift.

This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).

== briefs/v0.33.62__nfrs-brief-pack__05__boundaries-and-licensing.md