Example project — Frond is not real.

Authored demo content for a fictional plant-care app, rendered by the same parsers and held to the same invariants as a real project's dashboard. This is the system in use, three months in.

docs/phases/_system-template.mdWorkingactiveYYYY-MM-DDRead when: while this system phase is open (deleted at close — decisions.md carries the calls)
Frontmatter · 6 keys
category
phase
status
active
mode
system
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)

Levels: (none — one chat, kinds run in order | one level per kind: 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 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]

Decisions so far

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

Close items

  • 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)
  • mode-pure commit; board deleted