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.

Molds6

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.

Phase Name

Product
docs/phases/_product-template.md →

Fields it offers, in the frontmatter

status
active
tier
working
mode
product
last-reviewed
YYYY-MM-DD
read-when
When any task is completed or blocked

Fields it offers, on the page

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

Sections it lays out

  • Open notes (phase-specific only)Canonical open process
  • Workstream A — NameHow to read the workstreams
  • Acceptance Criteria
  • Close notes (phase-specific only)Canonical close process

Queue-shaping — [the friction] (ACTIVE)

Queue-shaping
docs/phases/_queue-shaping-template.md →

Fields it offers, in the frontmatter

category
phase
status
active
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

Mode
queue-shaping · the rituals this board runs
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
  • Close items

[Sweep — P## · P## · P## | Explore §N | Research: topic] — opened YYYY-MM-DD

Side
docs/phases/_side-template.md →

Fields it offers, in the frontmatter

category
phase
status
active
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

Mode
side · the rituals this board runs
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
  • Notes
  • Verify at close

System Work — [name] (ACTIVE)

System
docs/phases/_system-template.md →

Fields it offers, in the frontmatter

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)

Fields it offers, on the page

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)

Sections it lays out

  • Session open — YYYY-MM-DD
  • Items
  • Decisions so far
  • Close items

Phase Name — Walkthrough

docs/phases/_walkthrough-template.md →

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 in

How 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

Phase Name — {product | system | side | queue-shaping} seed

docs/planning/queued/_seed-template.md →

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
Explains itself in

How 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