
enforcement
Use when implementing hooks that BLOCK invalid actions, creating quality gates for state transitions, or enforcing tested:true verification. Load when designing enforcement mechanisms. Uses exit code 2 to block, JSON permissionDecision:deny, or updatedInput modification. Rules are instructions; h...
提供方 ingpoc|开源
Enforcement
Enforcement converts one already-proven invariant into a blocking control.
Procedure
- Identify the repeated invalid action and the existing deterministic assertion that detects it.
- Confirm the actual runtime owner: repository script, CI gate, Codex rule, plugin hook, operating-system sandbox, or external service policy.
- Place the block at the narrowest point before irreversible state change.
- Fail closed only for destructive, secret, security, or external-send boundaries. Keep ordinary routing and quality guidance informational unless the repository explicitly requires a block.
- Test an allowed case, a denied case, diagnostic output, and recovery after the condition is corrected.
- Document how to disable or remove the guard safely.
Boundary
determinismowns the machine-checkable assertion.enforcementowns where and how that proven assertion blocks an action.verifyreports readiness but does not create blocking runtime policy.
Runtime-specific hook schemas belong in the plugin or repository that implements them, not in this global skill.