verify-before-documenting

To prevent inaccurate documentation, you must verify code by searching files and reading source evidence before making claims about code state. This process enforces evidence-based assertions, ensuring all gap analysis and audit reports reflect actual implementation rather than assumptions.

Evidence-based documentation is a practice requiring explicit file reads and detailed evidence citation before asserting code state. It solves the problem of false assumptions during audits by guaranteeing all claims about code existence, absence, or state are backed by concrete codebase evidence.

To verify a missing feature, systematically search the codebase for relevant keywords, read the actual source files, and cite detailed evidence confirming the absence. This verification step ensures your gap analysis report is accurate and prevents costly mistakes based on false assumptions.

Yes, this verification approach scales for large codebase audits by enforcing systematic search and explicit file reads before any claims are made. It ensures truthfulness across extensive code reviews by requiring detailed evidence citation for every assertion about code state.

Code review documentation contains false assumptions when claims are made without explicit file reads and verification. Without enforcing an evidence-based process requiring detailed evidence citation, reviewers rely on memory or assumptions rather than actual code implementation, leading to inaccurate gap analysis.