How does the skill handle constraints that cannot be proven statically?

If a constraint is marked with proof_obligation: false or cannot be proven, the skill generates a plan for runtime validation or database-level enforcement to maintain integrity.

Can this skill assist with database schema design?

Yes, it identifies constraints that are best enforced by the database layer, such as unique indexes or referential integrity, and can suggest the necessary SQL or migration logic.

What information is included in the constraints-report.yaml?

The report includes the status of every constraint, the verification method used (e.g., construction, Lean proof, or runtime check), and specific evidence such as code snippets or file references.

What is a proof obligation in this context?

A proof obligation is a business constraint that requires a mathematical proof—usually via the Lean theorem prover—to ensure it remains true across all possible system states.

Engineering Constraint Verifier

Name: Engineering Constraint Verifier
Author: BellaBe

byBellaBe

•

Seguridad y Pruebas

Verifies business constraints and invariants by generating formal Lean proofs or planning runtime validation checks.

Acerca de

The Engineering Constraint Verifier is a specialized tool for ensuring software integrity by cross-referencing business specifications with implementation details. It automatically categorizes constraints into formal proof obligations or runtime checks, utilizing Lean theorem proving for static guarantees and generating robust validation plans for dynamic rules. By bridging the gap between specification and enforcement, it ensures that every business invariant, precondition, and postcondition is accounted for through formal evidence, generated code, or database-level constraints.

Características Principales

Static verification of invariants using Lean theorem proving and refined types
Automated categorization of constraints into formal proofs or runtime checks
11 GitHub stars
Mapping of system-level invariants to database-specific constraints and migrations
Planning and generation of runtime validation logic for dynamic business rules
Comprehensive verification reporting including coverage metrics and gap analysis

Casos de Uso

Mapping complex business rules to relational database integrity constraints
Proving mathematical invariants in financial systems like non-negative balances
Designing robust API contracts with automated pre- and post-condition checks

Acerca de

Características Principales

Static verification of invariants using Lean theorem proving and refined types
Automated categorization of constraints into formal proofs or runtime checks
11 GitHub stars
Mapping of system-level invariants to database-specific constraints and migrations
Planning and generation of runtime validation logic for dynamic business rules
Comprehensive verification reporting including coverage metrics and gap analysis

Casos de Uso

Mapping complex business rules to relational database integrity constraints
Proving mathematical invariants in financial systems like non-negative balances
Designing robust API contracts with automated pre- and post-condition checks