closure-mode-at-boundarieslisted

# Closure Mode at Boundaries ## The Insight The moment a phase of work finishes is exactly when you (or your agent) are most tempted to charge into the next thing without review. Nothing can be called "done" until someone has deliberately tried to break it — and you can't move to the next phase until this one is certified. That deliberate try-to-break-it pass is **closure mode**. Three cognitive modes: - **Build mode** — expand, construct, progress. - **Refinement mode** — optimize, tighten. - **Closure mode** — stress, invert, challenge, simulate failure. Closure mode is NOT continuous. It is a deliberate phase shift, invoked at completion edges, that produces an action list which the workflow MUST execute before re-entering build mode with the next vector. ## Recognition Closure mode applies when ANY of these hold: - A sprint, phase, or vertical-slice lock just completed in the current session. - A "what should we do next" decision surfaces 2+ candidate forks. - The user invokes team consultation or SME deliberation at a boundary. - The current message is the first prompt after a clean completion event. - A previously-authored "next step" is stale relative to recent product memory or research. Closure mode does NOT apply mid-implementation, mid-debugging, when working a single bounded scope, or when explicitly skipped. ## Workflow Two halves: a parallel SME swarm (the closure run), then a transition step that executes the swarm's output. Both required. Running on