| process | <kebab-case-name> | |
|---|---|---|
| owner | <who answers for this process> | |
| systems |
|
|
| status | active | active-with-gaps | broken | deprecated | |
| last_verified | YYYY-MM-DD |
Purpose: one sentence — what outcome this process exists to produce.
What starts it (user action / schedule / webhook /
Mermaid diagram + numbered steps. EVERY step cites implementing code: repo/path/file.ext:line.
Where state lives (tables, docs, queues) and which system is the source of truth. One SOT per fact; everything else is a derived copy and says so.
What breaks, how you'd notice, where the alarm is — or ⚠️ no alarm, which is a finding.
The exact commands/queries/click-paths that prove the process works today. Running these and updating last_verified is the maintenance ritual.
Known gaps and the choices not yet made, so readers know the edge of the map.