docs/phases/_system-template.mdWorkingactive | waiting | pausedYYYY-MM-DDRead when: while this system phase is open (deleted at close — decisions.md carries the calls)
Frontmatter · 7 keys
category
phase
status
active | waiting | paused
mode
system
stage
open | build | close
tier
working
last-reviewed
YYYY-MM-DD
read-when
while this system phase is open (deleted at close — decisions.md carries the calls)

System Work — [name] (ACTIVE)

Mode: system · the rituals this board runs

Project: (the repo this board lives in — work outside it gets handed over, not done) · Upgrade: (none | the template's changelog entries this phase takes in — anything here puts it in the upgrade kind, see CONTRIBUTING → The upgrade kind)

Levels: (none — one chat, kinds run in order | open high · build [tier] · close [tier], fires: [the Read when: triggers the close is expected to fire] — see CONTRIBUTING → The phase pipeline)

Session open — YYYY-MM-DD

  • Session title(s): (set at each chat's open and recorded here — Phase name · mode collapsed, one line per kind's chat when split: kind · Phase name · mode; ask only when the title is not derivable)
  • Friction named: [what this phase fixes, in one or two sentences]
  • Scope agreed with the PO: [what's in, what's out]
  • Settled calls this reopens: [entries from decisions.md / tiered docs this work touches — each is a structured challenge, logged win or lose; "none" is a valid answer]

Items

  • [the changes this phase makes — governance docs, tracker formats, /system code]

Raised

What other boards found on this board's ground

Any board may write here; only this one drains it. An entry names what was found or changed, where, which board found it and when, and what this session owes. A note is never an item — read this section at your open, and where a ruling or a check is owed, author your own O or V item from it, then delete the entry. Crossing re-authors it, and that is how this board takes ownership. An entry owed to a kind this board has already passed sets it back there, paused at that kind. Undrained entries hold the close (CONTRIBUTING.md → Rules shared by all modes).

  • (what was found or changed) · Where: (file or route) · From: (board), (date) · Owes: (judge | verify | nothing, FYI)

Decisions so far

  • [logged in decisions.md as they're made — this mode writes there directly; mirror one-line pointers here]

Close items

  • ## Raised drained — the section empty: every entry read, its own item authored where one was owed, the entry deleted (CONTRIBUTING.md → shared rules)
  • Hand off for verification — present the durable record (decisions entries + surface/build state); board not deleted until the PO confirms
  • implementation/system-surface.md / CONTRIBUTING updated if the system's behavior changed
  • last-reviewed bumped on every doc reviewed (not mechanically touched)
  • The next opening line handed off — the starter shape and mode, the name, one sentence of why, and where its context already sits; a pointer, not a briefing, and "nothing next" is a real answer (CONTRIBUTING.md → shared rules)
  • mode-pure commit; board deleted