epistemic-context-grounding

To verify implementation assumptions, you must enumerate them explicitly and perform a falsifiability check against canonical source documentation. This grounding process prevents over-engineering by ensuring design decisions are validated by domain knowledge before development proceeds.

Grounding design decisions in a new domain requires querying relevant documentation to understand context, listing all assumptions, and grading their verifiability. This ensures implementation choices are solid and based on canonical sources rather than unknowns.

Preventing over-engineering when parsing data formats requires assessing context sensitivity and verifying assumptions against canonical specifications. By making assumptions explicit and checking them against domain knowledge, you avoid wasted implementation effort.

Integrating with external systems requires assumption enumeration because unknowns can cause severe implementation mistakes. Explicitly listing and grading the falsifiability of assumptions against canonical sources ensures your design decisions are solid before external integration.

You need a context sensitivity assessment when starting development tasks involving new domain entry, parsing data formats, or integrating with external systems. This assessment identifies existing documentation and grounds your implementation decisions in canonical sources.

Yes, you can check domain knowledge by searching for relevant documentation and specs within your context environment. This automated grounding process identifies existing canonical sources and verifies your assumptions before you proceed with implementation design.