Phase Name

Mode: product · the rituals this board runs

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

Thesis: (run boards only — the run in one sentence: the change it sets out to make; delete on a member or standalone board)

Goal: One sentence: what the close leaves behind. Never the criterion — that lives in Acceptance Criteria.

Picture: (run boards only — planning/-picture.md, the one-frame view of the run, written by the open kind from _run-picture-template.md and reconciled at the close; delete on a member or standalone board)

Levels: (none — one chat, kinds run in order | one level per kind: open high · build [tier] · close [tier], or in a run open high · basic layer [tier] · survey high · deepen [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's 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)

Considered

Run boards only — delete on a member or standalone board

The alternatives and challenges weighed before building, written by the open kind: the shapes this run could have taken and why this one, the settled commitments it presses on and how each was raised. Decisions come from here; the survey re-reads it.

• (alternative or challenge — what was weighed, what won, why)

Survey

Run boards only — delete on a member or standalone board

Filled by the survey kind: the audiences walked, and the shown / launch / later table — what the site shows now, what must be good at launch, what waits. Its decisions land on this board's walkthrough and propagate at close. The member list below is the run's roster; each member names this run in its run:.

Members: (one board per chunk, with its stage: — the run board closes after the last of them)

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.

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)

Deepening

Member boards in a run — delete on a standalone board

What makes this surface good, written by the survey kind, plus the V items the basic layer wrote and did not walk. The deepen kind works from here and walks every item, device-tested. A new idea that arrives during the basic layer is filed here, never into the current build.

• (what the surface still needs, from the survey)
• (deferred V item — moved here unwalked at the basic layer's close)

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)