df:audit-milestone

To verify milestone completion against original intent before archiving, you can run an audit workflow that reads VERIFICATION.md files to confirm objectives were met during execution. This validates alignment with planned objectives and prevents context rot.

Aggregating tech debt and deferred gaps across milestones is handled by an audit workflow that reads project verification files. It collects outstanding technical debt and deferred items to ensure all gaps are documented before milestone archival.

An integration checker validates cross-objective wiring by spawning automatically during the milestone audit. It checks the connections between different project objectives to ensure all workflow gates are preserved and dependencies are not missed before archiving.

Yes, a VERIFICATION.md file is required to run the milestone audit. The audit workflow reads this file to confirm that project objectives were successfully verified during execution, ensuring alignment with original intent before archiving.

You should avoid archiving a project milestone without an audit when cross-objective wiring needs validation or tech debt remains unaggregated. Skipping the audit risks context rot, missed dependencies, and loss of alignment with planned objectives.