foundations-formal-methods
Formal Methods Foundations
Turn a requirement into a checkable property, pick the cheapest method that can catch the bug class, and report precisely what the evidence establishes. A verified finite abstraction is evidence about that abstraction; implementation correctness needs a demonstrated correspondence.
When to use
Triggers: "prove this protocol is correct", "write a TLA+ / PlusCal spec", "model check this workflow", "find a race condition formally", "verify with Z3 / cvc5 / Lean / Dafny / Verus", "TLA+ or property-based testing?", "check this LLM-generated proof or spec", "can any policy combination allow X", "safety versus liveness", "refinement mapping", "find a counterexample".
Not this skill:
- Routine unit tests or PBT harnesses belong to qa-testing-strategy.
- Consensus, replication and lease design, deterministic simulation, and Jepsen histories belong to foundations-distributed-systems.
- Hazard analysis of agent actions belongs to foundations-safety-engineering.
Use this skill when the specification, the choice of verification method, or the meaning of a result is the central question.
Quick Reference
Method ladder (full version in tool-selection.md):