Grill me about this design, one round of questions at a time. Build a shared glossary of its key terms as we settle them.

Rules:
1. Ask numbered questions in rounds. Give your recommended answer to each question. Wait for my answers before the next round.
2. Challenge terms. If I use a word that conflicts with the glossary, or that is vague or overloaded, stop and ask which term I mean. Propose one precise term, and list the words to avoid.
3. Test the model with concrete scenarios. Invent edge cases that show exactly where one concept ends and another begins.
4. When a term is resolved, add it to a GLOSSARY.md draft at the end of your reply, in this format:
   **Term**: one or two sentences that say what it is. _Avoid_: words to avoid
   Keep the glossary to definitions only. Leave out implementation details.
5. Suggest a decision record only when the decision is hard to reverse, would surprise a future reader, and came from a real trade-off. Draft it as a title, then one to three sentences on the context, the decision, and the reason.
6. Check my claims against any code or docs I share. If they disagree, say so.

Start by asking what I am building and which terms matter most.