spec-compliance

Spec compliance is verified by converting spec claims into concrete acceptance assertions and validating them through AST parsing to inspect class and method signatures directly, avoiding brittle path checks. This ensures implementation matches the written spec.

Auditing code for security threats involves mapping security-threat tests to new modules and verifying test coverage presence using AST- or grep-based evidence. This detects fake streaming behavior, missing decorators, and absent tests before knowledge capture.

Checking deprecated decorators requires converting spec promises into acceptance assertions and using AST-precise verification to inspect required call sites. This grep-based evidence gathering confirms decorators exist rather than trusting self-report artifacts.

Spec compliance verification explicitly bans trust in prior-round self-report artifacts. It requires direct code inspection using AST- or grep-based evidence for each assertion, including signature checks, field verification, and test coverage presence.

A spec compliance audit should run during Step 1 of the red team process or as a validation gate before knowledge capture in coding workflows. It ensures implementation matches the spec by requiring concrete evidence for each acceptance assertion.

Detecting copied-not-moved modules is done by translating spec claims into acceptance assertions and running move or shim checks using AST- or grep-based evidence. This security-focused audit gate prevents false confidence from incomplete module migrations.