01 · THE ROUTING LAYER
The index.
wiki/index.md
A catalog of every page in the wiki, refreshed on every ingest. Read this first — it tells you which page answers your question without scanning folders.
Seven sections in fixed order. Incidents sort newest-first; the rest are alphabetical.
What the file actually looks like
# Wiki Index Last refreshed: 2026-05-11 ## Incidents (3) - [[2026-04-12-checkout]] — SEV2, 31min, checkout-api - [[2026-03-14-checkout]] — SEV2, 47min, payments-db - [[2025-11-02-orders]] — SEV3, 22min, orders-api ## Services (4) - [[checkout-api]] — payments-team - [[orders-api]] — orders-team - [[payments-db]] — unknown - [[user-service]] — identity-team ## Root causes (2) - [[connection-pool-exhaustion]] — 2 incidents - [[downstream-slow-call]] — 1 incident ## Stubs to flesh out (2) - [[payments-db]] — referenced by 2026-03-14-checkout - [[fraud-scoring]] — referenced by 2026-04-12-checkout ## Open contradictions (1) - [[connection-pool-exhaustion]] — root-cause attribution differs between 2026-03-14 (SRE) and 2026-04-02 (payments)
Rules
- Refreshed on every ingest — counts, listings, stubs, and contradictions all update together.
- Each line is one wiki-link plus a short hook. No narrative, no paragraphs.
- Incidents are newest-first;
services,root-causes,concepts,ownersare alphabetical. - The trailing two sections surface debt — stubs that need writing, contradictions that need resolving.
- If a section is empty, keep the heading and write
(none). Don't delete sections. - A stale
Last refreshed:header means the wiki has drifted. Run an ingest or a lint.