← anatomy · knowledge · owners/
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.

payments-team 3 members · 2 services · 1 active rotation primary oncall today secondary Services owned [[checkout-api]] [[payments-db]] Recent incidents [[2026-04-12-checkout]] · [[2026-03-14-checkout]] · [[2025-11-02-orders]] no personal contact info — names omitted intentionally

Roles and rotation only. Names link to a separate, access-controlled directory.

What a page looks like

wiki/owners/payments-team.mdspecimen · trimmed
---
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

  1. Members — roles and rotation only. No names, emails, or handles.
  2. Services owned — bullet list, every service a wiki-link.
  3. Recent incidents — newest first, wiki-linked.
  4. Notes — cross-team rotations, on-call quirks, anything else.

Rules

  1. File name is the team slug in kebab-case, e.g. payments-team.md.
  2. Type-specific frontmatter: services, incidents.
  3. Never include personal contact info. Names, emails, phone numbers, chat handles — none of it. Point to the directory if needed.
  4. Recent incidents list mirrors what the incident pages claim in their owner: field. If they drift, lint will flag.
  5. Owner unknown? Don't create an empty owner page — leave owner: unknown on the consuming page and flag it.