batch-ask-me

# Batch ask me ## Contract | Field | Bound contract | |---|---| | Trigger | The user faces multi-fork decisions, unresolved prerequisites, or explicitly says "batch ask me" or "clarify the design space". | | Authority | Read-only: no file, VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | Conversation-only question batches and decision-tree state. | | Done | Frontier empty, all branches of the design tree visited, and shared understanding confirmed by the user. | ## Inputs The user's problem or design space to explore, stated in the conversation or inferable from it. Optional: any decisions already settled by prior context, which seed the design tree as resolved nodes. ## Procedure 1. Run Verbalized Sampling before round one. Sample multiple intent hypotheses, each with an explicit weight on a 0 to 1 scale and a concrete falsifier. Present the weighted hypotheses and falsifiers visibly, immediately before the first question batch. Seed the design-tree roots and initial frontier from the surviving hypotheses. Done when: the weighted hypotheses and falsifiers are presented and the design-tree roots and frontier are seeded. 2. Build a design tree where each node is a decision. The frontier is every decision whose prerequisites are already settled — the questions to ask now without guessing at answers not yet heard. Done when: the design tree is built and the frontier is computed. 3. Each round, ask the whole frontier as a batch of single-sel...