Molds7
The templates every board, walkthrough and seed is created from. A mold is met as a file you are already filling in, so what it offers is what gets filled in — a field it never lists is a field nobody knows is there.
Fields it offers, in the frontmatter
- status
- active | waiting | paused
- tier
- working
- mode
- product
- stage
- open | build | basic-layer | survey | deepen | close
- run
- " | [the run name]
- last-reviewed
- YYYY-MM-DD
- read-when
- When any task is completed or blocked
Fields it offers, on the page
- 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/<run>-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
Sections it lays out
- Open notes (phase-specific only)Canonical open process
- ConsideredRun boards only — delete on a member or standalone board
- SurveyRun boards only — delete on a member or standalone board
- Workstream A — NameHow to read the workstreams
- RaisedWhat other boards found on this board's ground
- DeepeningMember boards in a run — delete on a standalone board
- Acceptance Criteria
- Close notes (phase-specific only)Canonical close process
Fields it offers, in the frontmatter
- category
- phase
- status
- active | paused
- mode
- queue-shaping
- tier
- working
- last-reviewed
- YYYY-MM-DD
- read-when
- while this queue-shaping phase is open (deleted at close — the rows and seeds are the record)
Fields it offers, on the page
- Project
- (the repo this board lives in)
- Session title
- (set at open and recorded here —
Phase name · queue-shaping; this mode never splits; ask only when the title is not derivable)
Sections it lays out
- Session open — YYYY-MM-DD
- Rows shaped
- RaisedWhat other boards found on this board's ground
- Close items
Fields it offers, in the frontmatter
- category
- phase
- status
- active | paused
- mode
- side
- tier
- working
- last-reviewed
- YYYY-MM-DD
- read-when
- board close (deleted at close — the moved tracker rows + the commit are the record)
Fields it offers, on the page
- Project
- (the repo this board lives in — work outside it gets handed over, not done)
- Session title
- (set at open and recorded here —
Phase name · mode; side phases never split; ask only when the title is not derivable)
Sections it lays out
- Items
- RaisedWhat other boards found on this board's ground
- Notes
- Verify at close
- Next
Fields it offers, in the frontmatter
- 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)
Fields it offers, on the page
- 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)
Sections it lays out
- Session open — YYYY-MM-DD
- Items
- RaisedWhat other boards found on this board's ground
- Decisions so far
- Close items
Fields it offers, in the frontmatter
- status
- active
- tier
- working
- last-reviewed
- YYYY-MM-DD
- read-when
- Update as items are walked, edit as scope adjusts
Explains itself inHow this works — the card the mold carries above its first section.
Sections it lays out
- Open for your call
- Worth verifying
- Surfaces to glance (usually skip)
- Decisions surfaced during walkthroughBefore you write items — then delete this card
Fields it offers, in the frontmatter
- category
- planning
- status
- active
- tier
- working
- last-reviewed
- 2026-09-13
- read-when
- opening, surveying or closing the run this picture belongs to — a reading aid, deleted at the run's close
- run
- [the run name]
Explains itself inHow this works — the card the mold carries above its first section.
Sections it lays out
- The loop
- The aspirational site map
- Who owns which partsBefore you fill this in — then delete this card
Fields it offers, in the frontmatter
- category
- planning
- status
- queued
- tier
- working
- last-reviewed
- YYYY-MM-DD
- read-when
- when work touches this phase's territory — append a dated note; at phase open, fold into the board and delete this file
- mode
- product | system | side | queue-shaping
- phase
- Exact ROADMAP row name
- queued
- YYYY-MM-DD
- priority
- low | medium | high
- run
- " | [the run name — rows sharing it read as one group on the roadmap]
Explains itself inHow this works — the card the mold carries above its first section.
Sections it lays out
- Notes & finds
- Settled & open
- Candidate scope
- Refs
Source: CONTRIBUTING.md → A mold explains itself in one card — the convention; each mold above is its own source