adv-instructions-audit

To audit technical documentation for drift, systematically map load-bearing claims in instruction prose to executable test anchors. This verifies that documentation remains synchronized with code-level invariants and protocol rules.

Documentation drift occurs when instruction prose like AGENTS.md becomes disconnected from actual executable system behavior. Auditing prose against executable anchors detects contradictions between claims and underlying invariants.

Verify instruction prose coverage after a refactor by running a fidelity audit to ensure every protocol rule has a corresponding passing test anchor. This prevents silent failures in your engineering contract.

Yes, docs-as-code auditing applies to files like AGENTS.md and project.md by systematically mapping load-bearing claims to drift-guard tests. This maintains an accurate engineering contract between prose and system invariants.

The best way to maintain engineering contracts is systematic fidelity auditing, which maps instruction prose claims to executable test anchors to detect drift and ensure documentation matches protocol rules.