Specification Clause Violation detector

A requirement, story, or ticket can contain a blocking clause bound to an exact code symbol and a reviewed tree-sitter checker. Helen evaluates that checker against the pull-request head.

The check fails only when exact gating is enabled, the clause is accepted and blocking, its binding is current, calibration passed, and complete deterministic evidence proves a violation.

Helen preserves the source clause, symbol anchor, checker identity, current fingerprints, verification outcome, static observation, graph audit record, and the reason behind the enforcement decision.

Every missing or probabilistic input has an explicit neutral reason. Unavailable evidence never becomes a fabricated pass or a blocking failure.

Change the implementation to satisfy the accepted contract. If the contract itself is wrong, revise and review the specification through the product authority path before changing its enforcement.