spec-alignment-audit

You can verify design bundle compliance by running four automated checks for token contract alignment, surface inheritance coverage, primitive/verification-manifest coverage, and out-of-scope contradiction detection against your canonical spec file.

Spec alignment auditing prevents design bundles from shipping the wrong decisions by catching silent contract drift that internal consistency checks miss, verifying that chosen directions honor binding contracts before opening transcription PRs.

Run a spec alignment audit after your design bundle passes design-bundle-audit and before opening a transcription PR, or whenever a spec changes and you need to save the bundle direction as durable evidence alongside a compliance verdict.

Out-of-scope leakage detection flags contradictions where the bundle redesigns or removes spec-mandated fixed items, citing evidence from specific spec sections and bundle file:line references to prove the violation.

Yes, you need a verification manifest to check primitive coverage because the audit ensures each binding contract has a measurable hook that is covered, deferred with rationale, or blocked according to the manifest.

A GREEN/YELLOW/RED compliance verdict indicates your design bundle's level of spec alignment, accompanied by evidence-backed findings citing spec sections and bundle file:line references to justify the final compliance status.