03 · KNOWLEDGE
owners/
wiki/owners/{owner-slug}.md
One page per team. Members and rotation, services owned, recent incidents. Teams, not individuals — and no personal contact info, ever.
Roles and rotation only. Names link to a separate, access-controlled directory.
What a page looks like
--- type: owner name: payments-team status: reviewed services: [checkout-api, payments-db] incidents: [2026-04-12-checkout, 2026-03-14-checkout] tags: [team] last_updated: 2026-04-26 --- ## Members - primary oncall (week-on / week-off rotation) - secondary oncall (escalation) - team lead (business hours only) # contact info lives in the directory, not here ## Services owned - [[checkout-api]] - [[payments-db]] ## Recent incidents - [[2026-04-12-checkout]] — SEV2, 31min - [[2026-03-14-checkout]] — SEV2, 47min - [[2025-11-02-orders]] — SEV3, 22min ## Notes Shares pager rotation with [[orders-team]] on weekends.
Sections — in order
- Members — roles and rotation only. No names, emails, or handles.
- Services owned — bullet list, every service a wiki-link.
- Recent incidents — newest first, wiki-linked.
- Notes — cross-team rotations, on-call quirks, anything else.
Rules
- File name is the team slug in kebab-case, e.g.
payments-team.md. - Type-specific frontmatter:
services,incidents. - Never include personal contact info. Names, emails, phone numbers, chat handles — none of it. Point to the directory if needed.
- Recent incidents list mirrors what the incident pages claim in their
owner:field. If they drift, lint will flag. - Owner unknown? Don't create an empty owner page — leave
owner: unknownon the consuming page and flag it.