design-playbooklisted

# design-playbook **Design I/O** — same process every run: inject **declarations** (what good is), run **contracts** (how work enters the pipeline), **recirculate** failures to the declaration that owns them. Not a style library. For palettes/type catalogs use other packs; here the product pipeline and acceptance are the product. ## Run contract Keep each control in one authoritative place: | Control | Single source | Required content | | --- | --- | --- | | **Goal** | `spec` L1 | User-visible outcome, target user and scene, non-goals | | **Success** | `spec` L6 | Observable pass/fail criteria; every top-level L6 item is `Given -> When -> Then` | | **Evidence** | `spec` L6 + evaluator ledger | Exactly one `L6.<n>` ledger row per criterion; planning-only uses declaration coverage, implementation uses rendered states, interaction/test results, and applicable code checks | | **Stop** | this orchestrator | Pass; smallest missing decision; unavailable required evidence or authority; repeated blocker | | **Confirm** | this orchestrator + user decision | Any consequential action not already authorized | Answer, review, diagnose, and plan requests end with findings or a plan. Build and fix requests continue through in-scope local edits and the most relevant available validation. Ask the smallest question only when the answer changes the goal, scope, platform, success criteria, or authority; otherwise record a conservative assumption in L1. Pause for explicit confirmation befor