spec-implementation-diff

Verify spec compliance by cross-checking design notes and implementation summaries against verification reports to surface drift, omissions, and scope creep. This process enforces canonical governance rules and validates canonical documents, path resolutions, and status truthfulness.

Governance-aware spec implementation diff analysis identifies deviations between prescribed specifications and actual implementations while enforcing governance alignment. It analyzes design notes, implementation summaries, and verification reports to surface drift, omissions, and scope creep.

Check for specification drift before release readiness by analyzing design notes and implementation summaries against verification reports. This surfaces deviations, omissions, and scope creep while enforcing canonical governance rules including AH-006, BR-006, BR-008, and BR-009.

Yes, you can audit canonical documents including role-definition.md, package-spec.md, io-contract.md, quality-gate.md, and README.md for governance alignment. The analysis cross-checks these documents to verify path resolutions and status truthfulness across the implementation.

The best way to generate actionable diff reports for milestone validations is to run a diff between prescribed specifications and actual implementations. This generates a governance-aware report guiding reviewers and informing acceptance decisions by surfacing drift early.

You should avoid automated spec implementation diffing when canonical documents, design notes, implementation summaries, or verification reports are incomplete or missing. The analysis requires these inputs to accurately surface deviations, enforce governance rules, and validate path resolutions.