The wiki's anatomy.
Drop a postmortem in raw/ and the wiki has to do three jobs: route, remember, and hold the actual knowledge. Twelve pieces. One contract.
Routing
1 pieceThe first file you open. Without this, you'd be scanning folders. With it, you know which page answers your question before you click anything.
Memory
1 pieceThe wiki's diary. Newest on top, append-only, never rewritten. Every ingest gets one entry — what source came in, what pages changed, what conflicts surfaced.
Knowledge
5 piecesFive folders, one page per real thing. Incidents are concrete events; services and root-causes accumulate patterns across them; concepts and owners give the wiki a shared vocabulary and a chain of accountability.
incidents/
One page per incident — what happened, when, how it ended. Named YYYY-MM-DD-slug.
services/
One page per service. Upstream, downstream, known failure modes, incident history — the "what calls what" view.
root-causes/
One page per recurring cause. Multiple incidents collapse into one explanation — the most valuable cross-reference in the wiki.
concepts/
Definitions of terms referenced across the wiki — SEV1 vs SEV2, error budget, MTTR, paging policy.
owners/
One page per team. Members, services owned, recent incidents. No personal contact info — teams, not individuals.
Cross-cutting rules
4 piecesThe four contracts every page in the wiki obeys regardless of folder. Frontmatter shape, link syntax, stub conventions, and the one rule that keeps the wiki honest when sources disagree.
Frontmatter
The YAML block every page carries: type, name, status, owner, sources, source_hashes, tags, last_updated.
Wiki-links
Obsidian-style [[page-name]] references. Resolved by basename — which must be unique across the whole tree.
Stubs
Placeholder pages that exist only so wiki-links never dangle. Tracked in the index so they don't get forgotten.
Contradictions
The most important rule: when sources disagree, never silently overwrite. Log both versions, surface in the index.