Scope Check Before Design

Turn a request into either an implementation contract or a fully formed design. Classification comes first, always: one turn that states a hypothesis, records assumptions, and picks a route. Only Route C runs the full design cycle — A and B exist so an already-specified change is not taxed with a design.

Step 0 — Scope Check

Do this before any other action, in a single turn, for every request.

1. Hypothesis with confidence. One sentence naming what the user wants to end up with, plus an honest 0-100% confidence. Below 70%, add one line stating what is missing.
2. Assumption ledger. List the assumptions the answer rests on; mark each verified (confirmed in code or docs this session), assumed, or contradicted (checked and found false). Retrieve repository facts yourself; ask only user decisions. Any contradicted entry means Route C.
3. Classify against the route conditions below.
4. Announce the route in one self-contained sentence — it must repeat the target contract in full, with the literal values, names, and numbers from the request, and read correctly on its own.