grill-with-docs

Validating an architecture plan against a domain model requires stress-testing decisions by interrogating each branch against documented glossary terms in CONTEXT.md. This process involves iterative, single-question pacing to resolve dependencies until terminology conflicts are eliminated and shared understanding converges.

Requirements clarification through plan interrogation is a technique that walks down each branch of a design tree one question at a time until dependencies between decisions are fully resolved. It forces alignment with existing domain language and recorded architectural trade-offs.

You need to create an Architecture Decision Record when the design choice is hard to reverse, surprising without context, and involves a real trade-off. ADR creation is offered conditionally only when all three explicit criteria are met during the interrogation process.

Detecting terminology conflicts involves comparing proposed plan terms against your documented glossary in CONTEXT.md. Mismatched or ambiguous terms are challenged during interrogation, and CONTEXT.md is updated inline when terms are resolved, keeping it free of implementation detail.

Yes, domain-driven design terminology validation applies to architecture and integration discussions where terminology must match CONTEXT.md. It explores the codebase and docs when possible to ensure proposed integration plans align with recorded architectural decisions.