Formal Verification
Overview
Formal verification studies rigorous ways to show that systems satisfy properties such as safety, security, and correctness. It represents systems and requirements with logic, then uses theorem proving, model checking, SMT solving, static analysis, and runtime monitoring to prove properties or find counterexamples. These methods apply to software, hardware, protocols, neural networks, robotics, and AI agents, where failures can be costly and testing covers only selected executions. Current work combines automation and language models to reduce proof effort, but scalability and whether specifications faithfully capture intended behavior remain central challenges.
Latest papers 320
44 papers in the last four weeks, up 91% on the four weeks before. 0.3% of all new papers.
The LLMbda Calculus: AI Agents, Conversations, and Information Flow
Feedback-based Automated Verification in Vibe Coding of CAS Adaptation Built on Constraint Logic
VeriSoftBench: Repository-Scale Formal Verification Benchmarks for Lean
BMC4TimeSec: Verification Of Timed Security Protocols
M2F: Automated Formalization of Mathematical Literature at Scale
MerLean: An Agentic Framework for Autoformalization in Quantum Computation
Synthesis and Verification of Transformer Programs (Technical Report)
Formally Verifying and Explaining Sepsis Treatment Policies with COOL-MC
Doc2Spec: Synthesizing Formal Programming Specifications from Natural Language via Grammar Induction
LLMs versus the Halting Problem: Characterizing Program Termination Reasoning
MINIF2F-DAFNY: LLM-Guided Mathematical Theorem Proving via Auto-Active Verification
The 4/ Bound: Designing Predictable LLM-Verifier Systems for Formal Method Guarantee
CodeGen, Compilation, InvariantSynth, and SMTSolving. We prove that for any non-zero stage success probability (), the system reaches the Verified state almost surely. Furthermore, because of the sequential nature of the pipeline, we derive a precise latency bound of . We stress-tested this prediction in an extensive empirical campaign comprising over 90,000 trials. The results match the theory with striking consistency: every run reached verification, and the empirical convergence factor clustered tightly around , confirming that the bound accurately mirrors system behavior rather than serving as a loose buffer. Based on this data, we identify three distinct operating zones -- marginal, practical, and high-performance -- and propose a dynamic calibration strategy to handle parameter drift in real-world environments. Together, these contributions replace heuristic guesswork with a rigorous architectural foundation, enabling predictable resource planning and performance budgeting for safety-critical software.