devbooks-convergence-audit

A convergence audit validates completion claims by cross-checking verification.md, evidence/ directories, tests/, and git history. It surfaces false completions and weak signals to ensure every obligation has verifiable proof before archiving a change package.

Evidence-based convergence auditing is a verification process that cross-validates change packages against completion claims. It analyzes verification.md, evidence/, tests/, and git history to produce an audit report, credibility score, and remediation list.

Audit fake green signals by running a convergence audit that cross-checks git history and tests/ against verification.md claims. It identifies misleading statuses and outputs a credibility score with a remediation list to guide required evidence supplementation.

Yes, convergence auditing validates major change packages before archiving by cross-checking verification.md, evidence/, tests/, and code history. It ensures all obligations have verifiable evidence and outputs a credibility score and remediation list.

A convergence audit outputs an audit report, a credibility score, and a remediation list. These artifacts identify false completions and weak signals, guiding developers on required rework and evidence supplementation to prove convergence.