requirement-to-tlaplus-property-generator

TLA+ formalization distinguishes safety properties, which define states that must never occur, from liveness properties, which define states that must eventually occur. The Skill classifies natural-language requirements accordingly to generate checkable TLA+ invariants and temporal formulas.

You formalize a safety requirement by mapping natural-language concepts to TLA+ state variables and extracting state predicates. The system uses a pattern catalog to translate phrasings like 'never allow concurrent access' into a checkable TLA+ invariant.

Yes, you can convert informal acceptance criteria into temporal formulas for TLA+ model checking. The system extracts state predicates from requirements and applies temporal logic to generate checkable liveness properties and precedence constraints.

Yes, understanding TLA+ syntax is required. The formalization process requires knowledge of TLA+ syntax for safety, liveness, and precedence constraints to accurately translate informal requirements into checkable predicates.

The best way to formalize liveness properties is to classify the requirement as a liveness condition and map it to TLA+ temporal formulas. The system translates informal statements of eventual outcomes into checkable predicates for TLA+ model checking.