Vertical Slice

Open Plan (and the CharterPlan inspector) edits the vertical slice as a definition form plus an exit-criteria checklist, not two unlabeled dumps. Completeness still only requires a filled slice brief.

No extra menu. Use ArTchie / Charter / Open Plan.

MiniLabel: a vertical slice is one polished, representative playable slice before you scale.

Definition

Field	Role
Brief	What this slice is. Completeness still uses this field.
Target duration	String, e.g. 8–12 minutes
Must-represent systems	Systems this slice has to show — not the full game
Polish bar	What “done” looks like visually and in feel

Empty fields stay empty. Charter does not invent a playable path. One-Page GDD still seeds short [prompts] you replace.

Exit-criteria checklist

Each row is a toggle + text. Add row / Remove. Empty rows are allowed and do not count toward the summary.

Summary miniLabel: N / M exit criteria checked (M = rows with non-empty text; N = those rows that are checked).

The old Exit notes textarea (exitCriteria) stays as optional free-text so existing plans remain valid. The checklist is List<CharterSliceExitItem> (text + done).

Completeness

Required one-page list is unchanged: still Slice brief. The checklist is not a required one-page check. An informational ≥1 exit criterion miniLabel appears in Completeness when M is 0.

Templates

• Blank — empty definition fields, empty exit notes, 0 checklist rows.
• One-Page GDD — brief is the playable path only. Duration / must-represent / polish-bar / exit-notes have their own short [prompts]. Seeds 5 unchecked prompt rows: core loop playable, one pillar proved, polish bar met, duration hit, no blocker bugs in the slice.

See Documentation/OpenPlan.md, Documentation/OnePageGdd.md, and Documentation/PlanAsset.md.