DocProof

Documentation rot is one of the most quietly expensive problems in software: READMEs claim Node 18 while package.json requires Node 20, .env.example is missing a required key, API docs describe endpoints that no longer match the code. Nobody notices until a new hire wastes a day debugging an environment that was "documented correctly." DocProof turns every documentation claim into a Documentation Contract — a structured object with a source, a claim, an expected value, an actual value, a pass/fail status, and evidence. Powered by IBM Bob 2.0's Agent Mode, a central orchestrator dispatches four specialized subagents in parallel (Runtime Requirements, Commands, Config/Env, API Docs), each independently verifying one area of the target repo against its documentation using Bob's Document Understanding to extract claims from README, docs, and specs. When a mismatch is found, DocProof doesn't just flag it — it generates a suggested fix, routes it through a human Approve/Reject step, and re-verifies automatically once approved, closing the loop: Problem → Evidence → Fix → Approval → Re-verify. The result is a live Documentation Trust Score that the team can watch improve in real time. On our demo repo, running the full pipeline caught 3 deliberately planted inconsistencies (Node version, Python version, a missing SECRET_KEY), generated fixes for all of them, and raised the Trust Score from 52.5 to 57.5 after a single approved fix cycle — with zero duplicate contracts and fully refreshed evidence on every corrected item. DocProof isn't a linter. It's a standing, provable guarantee that what your docs say is what your code actually does.