grill-melisted

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask the questions one at a time, waiting for feedback on each question before continuing. If a question can be answered by exploring the codebase, explore the codebase instead. ## Domain awareness During codebase exploration, also look for existing documentation: ### File structure Most repos have a single context: ``` / ├── context.md ├── .ai/ │ └── docs/ │ └── adr/ │ ├── 0001-event-sourced-orders.md │ └── 0002-postgres-for-write-model.md └── src/ ``` If a `context-map.md` exists at the root, the repo has multiple contexts. The map points to where each one lives: ``` / ├── context-map.md ├── .ai/ │ └── docs/ │ └── adr/ │ └── 0001-event-sourced-orders.md ├── src/ │ ├── ordering/ │ │ └── context.md │ └── billing/ │ └── context.md ``` Create files lazily — only when you have something to write. If no `context.md` exists, create one when the first term is resolved. If no `.ai/docs/adr/` exists, create it when the first ADR is needed. ## During the session ### Challenge against the glossary When the user uses a term that conflicts with the existing language in `context.md`, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — wh