invariant-ace

What problem does it solve?

This Skill helps teams transform vague safety expectations into concrete, enforceable invariants that prevent invalid states across data, protocols, and algorithms. It focuses on owning specific state and boundary mutations, then proving correctness through counterexample traces and explicit verification signals.

Core Features & Use Cases

• Invariant discovery and ownership: identify the state owner and the transitions that must preserve P(state).
• Inductive safety enforcement: apply strong, cheap boundaries (parse/construct/API/DB/lock/txn) to keep the system safe.
• Counterexample-driven refinement: refine invariants via concrete traces and add observability to catch violations early.
• Use cases: prevent null/shape surprises, race conditions, stale data, and improper ordering in concurrent systems.

Quick Start

Use invariant-ace to structure an invariant plan for a sample module: define scope, owner, a minimal counterexample, and a single, enforceable boundary.