← Latest papers
🤖 AI

VeriAct: Beyond Verifiability -- Agentic Synthesis of Correct and Complete Formal Specifications

This paper introduces VeriAct, a verification-guided agentic framework that overcomes the limitations of prompt-based synthesis and the inadequacy of standard verifiers by iteratively refining formal specifications to ensure they are not only verifiable but also genuinely correct and complete.

Original authors: Md Rakib Hossain Misu, Iris Ma, Cristina V. Lopes

Published 2026-04-02
📖 4 min read☕ Coffee break read

Original authors: Md Rakib Hossain Misu, Iris Ma, Cristina V. Lopes

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a strict building inspector (the Verifier) checking a new house built by an architect (the AI).

In the world of software, "Formal Specifications" are like the blueprints and safety contracts for a program. They tell the computer exactly what the code must do and what it must not do. If the code follows these rules, the software is safe and reliable.

For a long time, people have tried to use AI to write these blueprints automatically. The problem? The AI often writes blueprints that look perfect to the inspector but are actually useless or dangerous.

Here is a simple breakdown of what this paper, VeriAct, discovered and how it fixed the problem.

1. The Problem: The "Passing Grade" Trap

The researchers found that current AI tools are great at getting a "Pass" from the inspector, but they are terrible at writing good blueprints.

  • The Analogy: Imagine you ask an AI to write a rule for a door: "The door must be open."
    • The Inspector's View: The inspector checks the door. It is open. The rule is satisfied. PASS!
    • The Reality: The rule is useless. It doesn't say when the door should be open, or what happens if it's raining. It doesn't stop the door from being open when you want it closed.
    • The Paper's Finding: AI models were writing "trivial" rules (like "The door is open") that technically passed the test but didn't actually describe how the software should behave. They were "gaming the system."

2. The First Attempt: Tweaking the Instructions (Prompt Optimization)

The researchers tried to fix this by giving the AI better instructions (called "Prompt Optimization"). They used a smart system called GEPA that acted like a coach, telling the AI: "You got a pass, but your rule was too vague. Try again."

  • The Result: The AI got better at passing the inspector's test.
  • The Catch: It hit a ceiling. Even with the coach, the AI was still writing rules that were too simple or missed important details. It was good at looking correct, but not being correct.

3. The New Tool: Spec-Harness (The "Stress Test")

The researchers realized the inspector (the Verifier) was too easy to fool. They needed a new tool to check if the blueprint was actually complete and accurate. They built Spec-Harness.

  • The Analogy: Instead of just asking the inspector, "Is the door open?", Spec-Harness is a Stress Test.
    • It tries to break the door. It asks: "What if someone pushes the door when it should be locked? Does your rule stop them?"
    • It checks: "If I change the temperature outside, does the rule still hold?"
    • The Shocking Discovery: When they used Spec-Harness, they found that most of the blueprints the AI wrote (even the ones that passed the inspector) were actually broken. They were either too weak (letting bad things happen) or too strong (stopping good things from happening).

4. The Solution: VeriAct (The "Self-Correcting Architect")

Since the AI couldn't just be "told" to do better, the researchers built a new system called VeriAct. Think of VeriAct as an Architect with a built-in Quality Control Team.

Instead of just writing a blueprint and handing it over, VeriAct works in a loop:

  1. Draft: The AI writes a rule.
  2. Inspect: The Verifier checks if it's legal.
  3. Stress Test: Spec-Harness tries to break it.
  4. Feedback: If the rule is too weak or too strong, VeriAct tells the AI exactly where it failed.
  5. Repair: The AI rewrites the rule based on that specific feedback.
  6. Repeat: It keeps doing this until the rule is not just "legal," but actually perfect.

The Bottom Line

  • Before: AI wrote rules that tricked the inspector but failed in the real world.
  • After (VeriAct): The AI acts like a careful engineer. It writes a rule, tests it against thousands of "what-if" scenarios, fixes its own mistakes, and only stops when the rule is truly robust.

In short: The paper proves that just because code passes a test doesn't mean it's good. To get truly reliable software, we need AI that doesn't just pass the test, but actively hunts for its own mistakes and fixes them until the job is done right.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →