← Latest papers
💻 computer science

Proof Theory and Dependent Type Theory: Distinct Foundations for Designing Proof Assistants

This paper argues that modern structural proof theory, exemplified by the sequent calculus and implemented in the Abella theorem prover, offers a compelling alternative to dependent type theory for designing proof assistants by better separating logic from proof structure, strategically utilizing non-determinism, avoiding complex typing issues, and providing an elegant approach to handling bindings.

Original authors: Dale Miller (Inria Saclay,LIX, Institut Polytechnique de Paris)

Published 2026-07-15
📖 6 min read🧠 Deep dive

Original authors: Dale Miller (Inria Saclay,LIX, Institut Polytechnique de Paris)

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 trying to build the ultimate "Proof Assistant"—a super-smart robot that helps humans check their math and logic homework to make sure it's 100% correct. For decades, most of these robots have been built using a specific blueprint called Dependent Type Theory (DTT). It's like building a robot out of a very complex, high-tech Lego set where every single brick has a specific label, and the robot checks if the labels match perfectly before letting you snap them together.

But in this paper, author Dale Miller suggests that there's another, perhaps better, way to build these robots. He argues that we should look at Structural Proof Theory, specifically a framework called the Sequent Calculus. Think of this not as a rigid Lego set, but as a dynamic, moving puzzle where the pieces can slide around and change shape as long as the logic holds up.

Here is the breakdown of why Miller thinks this "puzzle" approach might be superior to the "Lego" approach, using six key ideas:

1. Separating the "What" from the "How"

In the Lego world (DTT), the robot decides two things at once: what logic you are using and how the proof is built. It's like saying, "We are only allowed to build towers using red bricks, and the only way to stack them is straight up."
Miller suggests we should separate these. We can decide on the logic (the rules of the game) and then choose any proof structure we want to solve it. It's like deciding you want to play soccer, but then realizing you can score goals by kicking, heading, or even using a net-cannon if the rules allow. The Sequent Calculus lets you use many different "moves" (like natural deduction, tableaux, or resolution) without forcing you into a single, rigid style.

2. The Problem with "Proofs as Code"

The Lego approach treats a proof like a computer program (a λ-term). While computers are great at running programs, they can be picky. Sometimes, the program takes a weird path to get to the answer, or it gets stuck because it's waiting for a specific type of input.
Miller points out that the Lego approach has to deal with messy issues like "universe levels" (a complex way of organizing types so they don't crash into each other) and "proof irrelevance" (wasting time checking parts of the proof that don't actually matter). The Sequent Calculus approach is simpler; it doesn't need to worry about these heavy typing rules because it treats the proof structure more directly, like a flowchart rather than a complex code script.

3. Handling "Classical" Logic (The Either/Or Problem)

Some logic is "intuitionistic" (you must prove something exists by building it), and some is "classical" (you can prove something exists just by showing it's impossible for it not to exist).
The Lego approach struggles to handle the "classical" style smoothly. It often has to add extra, clunky rules to make it work. Miller argues that the Sequent Calculus was designed from the start to handle both styles equally well, like a universal adapter that fits any plug without needing a bulky converter.

4. Embracing "Maybe" (Non-Determinism)

This is a big one. The Lego robots are built to be "deterministic," meaning they must follow a single, straight path to check a proof. If they hit a dead end, they stop.
Miller suggests that allowing a little bit of "non-determinism" (guessing and backtracking) is actually a superpower. Imagine a maze. A deterministic robot walks one path and stops if it hits a wall. A non-deterministic robot can try a path, hit a wall, say "oops," and instantly try a different one.
Miller argues that by letting the proof-checker "guess" and backtrack, we can make the "proof certificates" (the homework you hand in) much smaller. The robot does the heavy lifting of searching, so you don't have to write down every single step. It's a trade-off: a smaller homework sheet for a robot that has to think a bit harder.

5. The Magic of "Moving Binders"

This is the paper's most exciting trick. In logic, we often deal with variables that are "bound" (like the "x" in "for all x..."). In the Lego world, these variables are often stuck in place, and handling them is a nightmare of technical headaches (like the famous POPLMark challenge).
Miller proposes a view where these variables are mobile. He calls this λ-tree syntax.
Imagine a variable is a name tag on a person. In the Lego world, if you move the person, the name tag might fall off or get confused. In Miller's world, the name tag is glued to the person. No matter how you move the person around the room (or the proof), the name tag stays with them.
He introduces a special tool called the ∇-quantifier (pronounced "nabla"). Think of this as a "local scope" button. When you press it, it says, "This variable belongs only to this specific part of the proof, and it can never escape." This makes it incredibly easy to reason about languages that have complex rules, like programming languages or the π-calculus (a way to model how computers talk to each other).

6. The Abella Robot

Miller doesn't just talk about this; he built a robot to prove it works. It's called Abella.
Abella is a theorem prover built entirely on these Sequent Calculus principles. It uses the "moving binders" and the ∇-quantifier to handle complex logic about languages and bindings with ease. While the Lego-based robots (like Coq or Lean) are very popular and have huge libraries of pre-built proofs, Abella suggests that for certain tricky problems—especially those involving how variables are named and moved around—this new approach is more natural and elegant.

The Bottom Line

Miller isn't saying the Lego robots (Dependent Type Theory) are bad or that they should be thrown away. He acknowledges they are mature, widely used, and great for many things.
However, he suggests that for the foundations of how we design these proof assistants, the Sequent Calculus offers a more flexible, simpler, and more powerful toolkit. It separates logic from structure, embraces smart guessing, and handles the tricky business of "moving variables" with a elegance that the current standard struggles to match. It's an invitation to look at the problem from a different angle, using a framework that has been successful in many other areas of logic but hasn't yet taken the spotlight in the world of interactive proof assistants.

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 →