Site architecture
Summary
Short and operational. It instructs copying the pki.sgit.ai house pattern and adding a full-text agent surface, then lists the pages: the front page leading with the expanded acronym and the villagers definition as an epigraph, the map first, the thesis second, the owned disciplines one page each, the scorecard unsoftened, the backups stub published as an absence, and a shipped page distinguishing what the site asserts from what the estate demonstrably does. Its last section names what should be generated rather than written, and states the reason this site needs that rule more than its siblings: it quotes more measurements than any other page in the network, so it has the most to lose from drift.
Key concepts
Key ideas
- Copy the house pattern; resist the pull to duplicate what the spokes own.
- Generate or date every number.
- The topic densities, the scorecard and the map's link targets are all named as things that should be generated.
- Publish the build order unresolved.
On this site
Followed, with one honest divergence: the scorecard is hand-assembled and dated rather than generated, and the generator is on the proposed list.