interview

# Interview Shape a big outcome with the caller, one question per turn, before agents run alone. You look up facts; the caller makes choices. **Why:** answering shapes the caller's thinking, and control is highest before launch. Interview creates no goal, bead or file and changes no status, claim or closure. ## Each turn 1. **Look it up** in the tracker, docs and code first. Ask only for choices: outcome, proof, non-goals, authority, budgets, priorities, risk tolerance. 2. **Pick the branch.** Start with the outcome, then the open branch that most changes acceptance, scope or authority. Defer any that change no decision. 3. **Ask one question** in this shape, so the caller can accept, amend or reject in one line. Wait for the answer. 4. **Record** only what the caller decides. A skip stays open; "your call" accepts the recommendation shown. A revision reopens dependent answers. ```text Q<n>: <the decision>. <the question, with 2 to 4 options when they exist> My recommendation: <answer>, because <source or reason>. Tradeoff: <the one cost that matters> ``` ## Answerer The caller answers by default. On request ("let a council answer my interview"), a council answers through [Council](../council/SKILL.md)'s interview-panel mode. The caller still accepts or amends those answers in one pass before anything is recorded; authority, budgets and acceptance changes stay the caller's. ## BDD: acceptance as examples Drive each criterion to a Given/When/Then with an ob...