Invariant Ace

Mission

Turn "should never happen" into "cannot happen" with minimal, high-leverage changes: name the real state owner, define owned inductive predicates, prove a counterexample trace, choose the strongest cheap enforcement boundary, and attach verification that can falsify the invariant and the proposed enforcement.

This skill is discriminative, not decorative. An invariant proposal is a claim to adjudicate, not a mandate to add checks. A property may be true, useful, or reviewer-sounding and still be the wrong invariant, wrong owner, wrong scope, wrong phase, wrong witness, or wrong boundary.

Actuating composition

Within Actuating, the checked-in invariant review lens owns the lane's scope and return shape. Use that evidence-only contract, not a second authority workflow. Return concrete invariant/transition witnesses to Review Fold; Actuating retains selection, implementation, proof, and closure. Do not launch authority fanout, emit clearance packets, or require the standalone Invariant Gate. This section takes precedence over the standalone modes, gates, output templates, and companion routing below only within Actuating. Standalone invocation is unchanged; no review lane or proof obligation is added or removed.