spec-alignment-audit

What problem does it solve?

Prevents design bundles from shipping the wrong decisions by auditing bundle-vs-canonical-spec compliance, catching silent contract drift that internal consistency checks can miss.

Core Features & Use Cases

• Token contract alignment: Verifies every bundle token matches the spec’s allowed meanings and ranges.
• Surface coverage via inheritance matrix: Confirms every binding surface is referenced and assigned the correct family/root/markers as required by the spec.
• Primitive coverage using the verification manifest: Ensures each binding contract has a measurable hook (covered, deferred with rationale, or blocked).
• Out-of-scope leakage detection: Flags contradictions where the bundle redesigns or removes spec-mandated fixed items.
• Use cases: Before opening a transcription PR, when a spec changes, or when saving bundle direction as durable evidence alongside a compliance verdict.

Quick Start

Run the spec-alignment-audit on your design bundle after it passes design-bundle-audit by providing the bundle root path and the canonical spec file path, then review the GREEN/YELLOW/RED verdict and its evidence-backed findings.