Clarify Decisions

This is a reusable interview protocol, not a pipeline stage. Nested under a parent, stay in its conversation and checklist; standalone, own the interview until shared understanding. Follow Todos for checklist ownership.

Name and decide every silent assumption that could create debt or a wrong architecture. Leading words: open set, territory, card, problem lock, criteria, coverage map, close package. The map (prompts, plans, knowns) is not the territory (codebase, runtime, users, history).

The Iron Law — channel

EVERY QUESTION IS INLINE CHAT WITH FULL CONTEXT.
NEVER use AskUserQuestion, structured MCQ pickers, or any harness UI that
truncates labels, option text, or the "why this matters" line.