Back to Feed
Agents / Benchmarks & Evals

Building Formally Verified Software with AI Agents

Original: Vero: Can AI Agents Build Formally Verified Software Repositories?

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 2 concepts

Key Takeaways

  • AI agents are typically used for programming without correctness guarantees, leaving open whether they can manage multi-module codebases.
  • Vero evaluates agents in either proof-only mode or code-and-proof mode with full tool access.
  • GPT-5.5 (xhigh) passes 87.3% of specifications in code-and-proof and 85.8% in proof-only.
  • Ten benchmark instances resist all eight configurations across both modes.

Summary & Methodology Analysis

AI agents are increasingly deployed for writing code, but existing benchmarks typically focus on individual functions or evaluate proof generation using provided implementations. This leaves a gap regarding whether agents can handle coherent implementation and proof choices across real multi-module codebases. To answer this, the paper introduces a framework and benchmark evaluation for agents. The methodology relies on a structured sequence of steps executed by agents and supporting tools. First, an agent discovers, selects, and plans by listing all available declarations from the source repository, identifying which ones to include, computing their dependencies, and committing to specific Lean signatures and a module layout. Next, an executor agent translates per-module definitions in dependency order, followed by curator review. Specifications are drafted in natural language and formalised in Lean for Track 2 non-formal repositories. The system then runs automated structure and build checks alongside LLM-judged semantic reviews of specification intent and idiomatic Lean usage. Finally, benchmark evaluation is executed on agents in either proof-only mode or code-and-proof mode with full tool access. Regarding empirical performance, GPT-5.5 (xhigh) passes 87.3% of specifications in code-and-proof and 85.8% in proof-only. However, ten instances resist all eight configurations across both modes.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the main problem addressed by the paper?

AI agents are increasingly used for programming, but do not provide any guarantee on the correctness of generated code, and existing benchmarks focus only on individual functions or pre-provided implementations.

Q2. What system or framework is introduced?

The paper introduces Vero to evaluate whether AI agents can build formally verified software repositories.

Q3. How well does the best performing model score?

GPT-5.5 (xhigh) passes 87.3% of specifications in code-and-proof and 85.8% in proof-only.

Q4. What are the two execution modes evaluated in the benchmark?

Agents are evaluated in either proof-only mode or code-and-proof mode with full tool access.

Q5. How does the planning phase work in the Vero workflow?

The agent lists all available declarations from the source repository, identifies which ones to include, computes their dependencies, and commits to specific Lean signatures and a module layout.

Q6. How are per-module definitions translated?

They are translated in dependency order through an executor agent, followed by curator review.

Q7. What checks and reviews are run on the code?

Automated structure and build checks are run alongside LLM-judged semantic reviews of specification intent and idiomatic Lean usage.

Q8. What are the limitations regarding the verification ecosystem and corpus?

Vero currently targets Lean 4 only as its verification ecosystem, and the benchmark corpus favors code that translates cleanly into Lean, with concurrent or temporal protocols largely absent.

Q9. What limitation exists regarding the audit mechanism?

The audit mechanism certifies formal satisfiability but cannot ensure that specifications are semantically correct or complete.

Flag an issue

What is wrong with this summary?

What is wrong?