Documentation Claim Validator

Verify that what documentation says is actually true by extracting testable claims and checking them against the codebase. Complements doc-maintenance (which handles structural health) by handling semantic accuracy.

When to Use

• After significant code changes (refactors, renames, API changes)
• Before releases — catch docs that describe removed or changed behavior
• When onboarding devs report "the docs are wrong"
• As a periodic trust audit on project documentation
• After running doc-maintenance to go deeper than structural checks

Quick Reference