← Latest papers
🤖 AI

Inductive Deductive Synthesis: Enabling AI to Generate Formally Verified Systems

This paper introduces Inductive Deductive Synthesis (IDS), an agentic LLM system that jointly synthesizes implementations and formal proofs for distributed systems, achieving 100% success on key-value store specifications with significantly reduced time and cost compared to both human experts and state-of-the-art coding agents.

Original authors: Shubham Agarwal, Alexander Krentsel, Shu Liu, Mert Cemri, Audrey Cheng, Rui Meng, Tomas Pfister, Chun-Liang Li, Sylvia Ratnasamy, Aditya Parameswaran, Matei Zaharia, Ion Stoica, Mohsen Lesani

Published 2026-05-25
📖 5 min read🧠 Deep dive

Original authors: Shubham Agarwal, Alexander Krentsel, Shu Liu, Mert Cemri, Audrey Cheng, Rui Meng, Tomas Pfister, Chun-Liang Li, Sylvia Ratnasamy, Aditya Parameswaran, Matei Zaharia, Ion Stoica, Mohsen Lesani

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 building a complex, distributed system like a digital bank or a shared notebook that many people use at once. You need to make sure that if Person A writes a note, Person B sees it immediately, and no data ever gets lost or mixed up, no matter how chaotic the internet gets.

Traditionally, there are two ways to build this:

  1. The "Guess and Check" Way (Current AI): You ask a smart AI to write the code. It writes it, runs a few tests, and says, "Looks good!" But this is like checking a bridge by driving one car over it. It might hold for that car, but it could collapse under a truck. It doesn't guarantee safety for every possible scenario.
  2. The "Mathematical Proof" Way (Traditional Experts): You hire a team of human mathematicians and engineers. They don't just test the code; they write a formal mathematical proof that the code cannot fail, no matter what happens. This is incredibly safe, but it takes years of human effort and costs a fortune.

The Problem:
The paper says that even the smartest current AI agents (like Codex or Claude) fail at the "Mathematical Proof" way. They try to write the code first, then try to prove it later. This is like trying to build a house and then asking an architect to prove it won't fall down after the bricks are already laid. It's too hard, and they get stuck.

The Solution: Inductive Deductive Synthesis (IDS)
The authors created a new AI system called IDS (Inductive Deductive Synthesis). Think of IDS not as a single worker, but as a team of specialized architects and inspectors working in a tight loop.

Here is how it works, using a simple analogy:

The "Build and Inspect" Loop

Instead of building the whole house and then checking it, IDS builds a tiny bit of the house and immediately checks if that tiny bit is mathematically sound.

  1. The Deductive Team (The Builders): These AI agents try to write a small piece of code (like a door frame) and a small piece of the proof (a math sentence saying "this door frame is strong").
  2. The Inspector (The Proof Assistant): A strict, unblinking robot inspector (called Rocq) checks the work immediately.
    • If the math doesn't add up, the inspector says, "No, this door frame is weak," and the team stops immediately. They don't waste time building the rest of the house on a weak foundation.
    • If it passes, they move to the next tiny piece.
  3. The Inductive Team (The Strategists): Sometimes, the builders get stuck. They keep trying to build the same type of door, but the math never works. This is where the "Inductive" part comes in.
    • The Proposer: A strategist AI looks at the stuck point and says, "Hey, maybe we shouldn't build a wooden door; let's try a steel one." It suggests a new local fix.
    • The Reloader: If the whole strategy is wrong (like trying to build a house on a swamp), this strategist says, "Scrap this design. Let's start over with a completely different blueprint."

Why This is a Big Deal

The paper claims this system is a game-changer for three reasons:

  • Speed: It solved 7 different complex distributed system problems in about 6.8 hours. A human expert team would have taken months or years to do the same thing. That's roughly 200 times faster.
  • Success Rate: The best existing AI agents could only solve 2 out of 7 of these problems. IDS solved all 7.
  • Performance: Not only is the code correct, but it's also fast. In some cases, the code IDS generated ran 3 times faster than the best human-written versions. This happened because the AI explored more design options than a human usually would, finding a "sweet spot" that humans missed.

The Catch (Limitations)

The paper is very honest about what IDS cannot do yet:

  • It needs a perfect recipe: You still need a human expert to write the initial "specification" (the mathematical rules of what the system should do). If the recipe is wrong, the AI will build a perfect house that doesn't match what you wanted.
  • It's not a magic wand for everything yet: They tested it specifically on "Key-Value Stores" (a type of database). While they believe it could work on other things (like operating systems or encryption), they haven't proven it yet.

The Bottom Line

This paper introduces a new way to use AI that combines building and checking at the same time. Instead of asking AI to "write code and hope it works," it asks AI to "write code and prove it works, step-by-step."

It turns the process of creating "perfectly safe" software from a slow, expensive human marathon into a fast, automated sprint, potentially making the software we rely on (like banking apps or cloud storage) much safer and more reliable.

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 →