hypothesys

Interview the user relentlessly until you reach a shared understanding. This means making clear the hypothesis and premises, and the goal metrics to evaluate. Map this as a design tree: every decision branches into the decisions that hang off it.

Work in rounds like an interview. In the first round, the questions will be about things that are clear in the context; do not guess things you haven't heard yet. Ask every frontier question you think is necessary and give your recommended answer. Then wait for the user's answer for the next round.

❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>

---

❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>

Each round, the user's answers reshape the tree: settled decisions push the frontier outward and unblock questions that depend on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a later round, not this one.