The topic map
Summary
The hub's core artefact and the reason it exists. Each topic gets a position stated in a line, the best source for it, and an owner. Seven are owned outright by this site because they have no other home: testing, CI, documentation, the IFD methodology, budgets as a discipline, project management, and the resilience patterns. Five are linked and never restated, because a sibling site owns them: security domains, serverless and scalability, explainability's grounding ladder, architecture conventions, and the villagers market argument. One is neither, and the document says so plainly: backups is on the estate's own list and has no doctrine anywhere.
Key concepts
Key ideas
- The rule above the table: when a sibling has measured something, link the measurement rather than paraphrasing it.
- A hub that drifts from its spokes is worse than no hub.
- Consistency is split across three homes; the recommendation is that this site owns the requirement and names the three rather than merging them.
- Backups is dense in mentions and empty in doctrine, which reads as coverage.
On this site
Published as /map/, effectively in full. The deconfliction contract is enforced by the pre-release gate, which fails a discipline page that cites no sibling.