reversa-audit

Auditing intent drift involves cross-checking requirements.md, roadmap.md, and actions.md to identify contradictions and coverage gaps. This process flags severity-ranked inconsistencies for human review without modifying the original files.

A read-only cross-check compares your feature's requirements, roadmap, and actions artifacts to validate coverage and consistency without modifying them. It generates a traceable audit report classifying issues by severity.

You validate requirements coverage by cross-checking the documented roadmap and actions against the initial requirements. This identifies legacy coherence failures and terminology drift, outputting a full report to feature-dir/audit/cross-check.md.

Yes, you can generate a severity-ranked inconsistency report using strict read-only behavior. It compares your governance artifacts and writes atomic findings to a separate audit directory, ensuring your source files remain untouched.

The limitation of read-only policy alignment audits is that they only identify and report contradictions without automatically fixing them. Humans must manually resolve the flagged mismatches between requirements, roadmaps, and actions.

Yes, you need a .reversa/state.json file to perform a Reversa feature audit. The audit process requires this state file to derive the correct output_folder and forward_folder paths for writing the cross-check report.