How We Use This Wiki

Governance rules. Required fields, review cadence, what goes where.

Governance rules so this wiki doesn’t rot into a junk drawer the way most do.

The four mandatory fields on every page

Every page must show, at the bottom (or in frontmatter for MDX):

Last reviewed: YYYY-MM-DD · Owner: @Name · Status: active / draft / archived

Field	Meaning
Last reviewed	Date someone confirmed this is still accurate. Updated even if nothing changed.
Owner	A named human responsible for this page. Not “team X” — a person.
Status	active / draft / archived / scaffold / superseded
Audience	engineering / product / gtm / people-and-ops

Type	Review every
ADRs	When superseded; never delete
Standards	Quarterly
Runbooks	After every use + quarterly
Apps (catalog)	Monthly + when shipped
Postmortems	Never — they’re historical record
RFCs	At spec → implement transition
Meeting notes	Archive after 90 days unless still load-bearing

Content	Goes in
A choice that constrains the future	ADR
A proposed new feature	RFC (in product space)
A “how to fix when X breaks”	Runbook
A bug post-fix	Postmortem
A reference doc	Apps catalog, standards, references
Long-lived knowledge	Wiki (this site)
Ephemeral state	Sidekick threads, PR descriptions, Slack

Don’t create pages without an owner
Don’t write “X (TBD)” — write the page or don’t write the page
Don’t keep three different versions of a doc — supersede and link, never branch
Don’t paste raw meeting notes — write decisions only, not transcripts
Don’t write a page that duplicates something in the codebase (CLAUDE.md, .claude/rules/, README) — link instead

Use the standard templates in Templates (when migrated) to avoid reinventing structure.