code-tag-audit

To detect drift between code and feature specifications, extract domainspec tags from source files and compare them against the feature registry. This surfaces mismatches and validation gaps to ensure code-to-spec alignment.

Deterministic code-tag traceability ensures code-to-spec alignment by mapping code tags to documentation. You need it when validating domainspec annotations against a schema to maintain governance across annotated codebases.

You audit domainspec tags by running an extraction process against source files and corresponding SPEC.md documentation. This performs validation, drift comparison, and composability checks, outputting a structured report.

Yes, you can enforce strict validation rules for code-tag mappings using strict and warn modes. Strict mode fails governance checks on schema validation gaps, while warn mode surfaces drift without blocking quality gates.

Yes, code-tag auditing supports waivers for validation gaps. Waivers allow specific drift or composability issues to bypass strict quality gates, integrating structured reporting with existing governance processes.

The best way to check code-tag composability issues is to perform static analysis on domainspec-tagged source files. This identifies edge mapping conflicts and validation gaps against the feature registry schema.