Phase Name

Mode: product · the rituals this board runs

Project: (the repo this board lives in — work outside it gets handed over, not done)

Goal: One sentence describing what "done" looks like.

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)

Depends on: Previous phases or conditions.

Refs: [[doc-1]], [[doc-2]]

Open notes (phase-specific only)

Canonical open process — product-lifecycle.md → Opening a Product Phase is the single source of truth. Work through those steps; do not copy them here.

List below ONLY what's specific to THIS phase: how it serves the vision (checklist step 1), conflicts surfaced during the opening audit, docs re-checked, scope calls made at open.

• 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)
• Serves the vision by: (one line — from strategy/Vision.md, read at open)
• (other phase-specific open notes go here — delete this line)

Workstream A — Name

How to read the workstreams

Letters are creation-order IDs, not sequence — workstreams get added as the board runs, so don't read A→Z as priority. The close workstream is unlettered ("## Close items") and sits last, whenever it was written.

Acceptance Criteria

• Criterion 1
• Criterion 2

Close notes (phase-specific only)

Canonical close process — product-lifecycle.md → Closing a Phase is the single source of truth. Work through those steps; do not copy them here — that duplication is exactly what drifts.

List below ONLY what's specific to THIS phase: the feature docs it touched, outward-facing artifacts to graduate, punch-list items it closes, next-phase dependencies it satisfies. Per-decision doc targets live in the walkthrough's "Decisions surfaced" log.

• (phase-specific close notes go here — delete this line)