ho-designlisted

# Design Produce one file someone else can implement from with no access to this conversation. You do not write business code in this phase. ## Locate the change Read the project's own rules first — `AGENTS.md`, or whatever equivalent instruction file your host reads — then `.ho/protocol.md` and `.ho/config.yaml` if they exist. Change artifacts live in `.ho/changes/<id>/`. If more than one change is open and the request names none of them, list the candidates and ask which. Do not pick one, and do not do all of them. ## Settle the facts yourself File paths, function signatures, test commands, current behaviour: open the files and read them. Never hand back a question you could have answered by reading the project. ## Questions that block **A question whose answer changes the direction of the work stops this phase.** Write the design down to that point, put the question in `Open questions`, and stop. One question at a time — the one that changes the most. Reversibility is not a reason to answer it yourself. | Rationalization | Why it fails | |---|---| | "It's additive and reversible, so I'll pick one and flag it" | Reversible describes the code. The question is about what the number *means*. A wrong meaning gets acted on before anyone reverts anything. | | "No reply is possible in this run, so I have to decide" | Not being able to get an answer now is the reason to write the question down, not the reason to answer it. | | "The other reading already exists elsewhere,