interrogate-with-docs

Run an interrogation session that asks one question at a time with a recommended answer, exploring the codebase instead of asking when possible. Each answer is challenged against the existing CONTEXT.md glossary and contradictions with the code are surfaced immediately.

CONTEXT.md is a project glossary defining canonical domain terms with words to avoid, kept free of implementation details. Create it lazily at the repo root when the first term is resolved, or use CONTEXT-MAP.md when multiple bounded contexts exist.

Write an ADR only when all three conditions hold: the decision is hard to reverse, surprising without context, and the result of a real trade-off between genuine alternatives. If any condition is missing, skip the ADR to avoid documentation noise.

Create a CONTEXT-MAP.md at the repo root listing each context, its location, and its relationships with other contexts. Each context then keeps its own CONTEXT.md glossary and context-specific docs/adr directory for local decisions.

The approach depends on the user engaging with questions and confirming terminology, so it cannot enforce consistency autonomously. It also deliberately excludes implementation details from CONTEXT.md, so technical specifications must live elsewhere.