roster-formal-verify

Formal verification ensures provable correctness by using mathematical proofs through Rocq or Quint, replacing standard QA gates for critical tasks with deterministic checker re-validation and auditable evidence tiering. This provides full traceability between proofs, implementation, and user requirements.

Automating formal proof validation in a development pipeline requires a dedicated verification gate that detects the correct backend via capability tag scanning, delegates compilation, and re-runs the underlying checker itself to avoid relying on unverified self-reports from sub-agents.

Yes, you can use Rocq and Quint for automated formal verification of smart contracts. The system detects the correct backend via capability tag scanning and generates standardized evidence tiers, such as E0p for Rocq proofs or E0m for Quint model verification.

Evidence tiers work by categorizing verification outputs into auditable levels: E0p for Rocq proofs, E0m or E0m-abstract for Quint model verification, and E1 for declined verification. This ensures full traceability between formal proofs, implementation, and user requirements.

Deterministic checker re-validation is required because relying on unverified self-reports from sub-agents is insufficient for high-assurance software. The system delegates compilation and trace generation, then independently re-runs the underlying checker to guarantee provable correctness.

You need to replace standard QA with a formal verification gate when developing safety-critical embedded software or audited smart contracts that require provable correctness, deterministic validation, and auditable evidence of verification before proceeding to review and deployment.