superstack-cocreatelisted

# superstack-cocreate People can't describe what they want, but they recognize it on sight. Probes make recognition cheap — and a reaction is data only if you know exactly what it was reacting to. The description's deferrals (a spec tool when requirements turn out statable; a design-variant tool for visual artifacts) hold only when such a tool is actually installed — confirm it appears in this session's skill listing before handing off, and say so; absent, these rounds cover the ask. ## The round 1. **Name the single contested assumption this round tests.** One axis per round — probes that differ on several axes at once produce reactions nobody can decode. 2. **Write 2–4 probes: identical voice, format, and length** — one page hard cap, skimmable in about two minutes each — **differing only on that axis** (when format itself *is* the contested axis, format varies and everything else holds). Probes are presented in the conversation: they exist to be reacted to now, not kept — say so up front; only the ratified ledger persists. Example, for "design the webhook API": probe A versions per-tenant, probe B versions globally — same headings, same length, one section different. 3. **Present.** Picking none is information, not friction — name what's outside the menu (inception's rule), and treat "none of these" as the axis answered: say what it just excluded. 4. **Decode aloud, then ratify.** "You rejected B — I read that as <requirement>. Confirm or correct." **Nothing locks unra