In the 1960s, researchers dreamed of automatic theorem provers powerful enough to develop lengthy proofs of conjectures that no human was able to prove before. Some even thought these "mechanical mathematicians" would eventually replace flesh-and-blood mathematicians. However, for many decades, automatic provers remained too weak to help, let alone replace, mathematicians. Instead, mathematicians turned to computer algebra systems, which help not so much with proofs as with computations, and automatic provers turned to other application areas. These areas include hardware and software verification, either directly or via an interactive verification platform (for example, Atelier B, Dafny, F*, Frama-C, SPARK 2014, Spec#, VCC, Why3). In addition, automatic provers are used as back ends to general-purpose proof assistants (for example, ACL2, Coq, HOL, Isabelle, Lean, Mizar, PVS). As mathematicians are slowly embracing proof assistants, automatic provers are finally becoming useful to them, for discharging straight-forward but tedious proof tasks.

### Key Insights

As a simple example from elementary mathematics, consider the formula

The logical symbols ∧ and ⇒ mean "and" and "implies," gcd is the greatest common divisor, and | is the "divides" relation between two numbers (for example, *d* | *ab* means *ab* is divisible by *d*). Let us check a special case: If *a* = 12, *b* = 35, and *d* = 5, we have *a'* = 1, *b'* = 5, and indeed *a'b'* = 5 divides *d* = 5 and vice versa. Mathematicians can easily see that the formula holds in general, but to write a formal proof with an acceptable level of detail for a proof assistant can easily take 15 or 30 minutes. In contrast, automatic theorem provers can prove such formulas within seconds.

It would be nice if automatic provers could always prove or disprove whatever formulas we give them in reasonable time. However, as Alonzo Church^{11} and Alan Turing^{29} showed already in the 1930s, this is impossible because provability is undecidable. We need to accept that provers might run forever on some unprovable inputs. And even for provable inputs, provers might take too long. Here are some easy-looking formulas that we could not prove automatically in reasonable time only a few years ago:

Intuitively, it seems reasonable that the formulas should hold: The first formula follows by distributivity of summation over addition. The second formula states that if two functions *f* and *g* coincide at all points *x*, then they are in fact equal, and therefore they will be members of the same sets. The third formula states that membership in big *O* is invariant under application of a function *k* to *n.*

The reason why older provers time out on these formulas is that the formulas are higher order: They contain binders such as summation and big *O* as well as first-class functions (for example, the unapplied occurrences of *f* and *g*). In contrast, the most commonly used provers for this kind of problems (such as resolution provers, superposition provers, and satisfiability-modulo-theories solvers) are first order. Higher-order formulas need to be translated into first-order formulas before they can be understood by first-order provers. In principle, this translation works; in practice, the resulting first-order formulas are so large and convoluted that the first-order provers are overwhelmed and time out. The higher-order constructs are effectively lost in translation.

Next to the first-order provers, native higher-order provers have been researched and developed since the 1970s. They were designed to prove smaller and sometimes tricky formulas, but not to tackle larger, almost first-order problems emerging from interactive verification platforms and proof assistants.

In the past five years or so, a new generation of higher-order provers has emerged, consisting of E,^{31} cvc5,^{4} Leo-III,^{24} Vampire,^{8} veriT,^{4} and Zipperposition.^{30} Their characteristic feature is that they build on the best first-order technologies and extend them. With one of these provers, our system Zipperposition, we can now prove the three problematic formulas above in a few seconds, as well as much more difficult higher-order problems.

Our leading design principle has been to focus on a *graceful* extension of standard superposition,^{2} following Bjarne Stroustrup's zero-overhead principle: "What you don't use, you don't pay for."^{25} Accordingly, a strong higher-order prover should behave like a first-order prover on first-order problems, perform mostly like a first-order prover on mildly higher-order problems, and scale up to arbitrary higher-order problems.

In this paper, we will retrace the steps that led to the development of our prover Zipperposition and its proof system, called λ-superposition.^{5} We start by describing the underlying logical language.

### What Is a Logic?

Every prover is based on a logic, which can be used to express mathematical definitions and arguments. Indeed, one of the roles of logic is to provide a rigorous foundation for mathematics. Today, even if most mathematicians do not consciously use logic on a daily basis, they feel reassured to know that their definitions and arguments can be encoded in it. In computer science, we can use logic to specify systems and to express their properties. Sometimes two distinct languages are used for these two purposes, but with an expressive logic, we can use the same language for both. For example, you can define the syntax and semantics of a programming language in a logic and then use logical reasoning to provide rigorous answers to questions such as "Is the language deterministic?" and "Is its type system sound?"

There are many logics to choose from. We briefly look at two: first-order logic and higher-order logic. Each comes with a concept of provability. By definition, a theorem is a provable formula—a formula that has a proof, whether known or not.

We start with (classical) *first-order logic*, also called predicate logic. It constitutes a sweet spot between simplicity and expressiveness. It forms the basis of set theory, the traditional foundation of mathematics. It is also the logic underlying most automatic theorem provers. First-order logic is often what people refer to when they simply say "logic."

First-order logic distinguishes between terms and formulas. We can think of the formulas as Boolean expressions, whereas terms denote other values (for example, numbers, lists, and matrices). A term can be a variable *x*, a constant c, or a function f applied to arguments f(*a*_{1}, …, *a _{n}*), where the arguments are themselves terms. Terms are used as arguments of predicates p(

*a*

_{1}, …,

*a*) to form formulas, which represent Boolean values. Formulas can also be predicates p without arguments, or they can be constructed from other formulas by combining them using logical operators such as ¬, ∧, ∨, ⇒ as well the quantifiers ∀

_{n}*x*. … and ∃

*x.*…. The equality predicate is sometimes also considered part of first-order logic. It is written in infix notation:

*a*

_{1}=

*a*

_{2}. In addition, modern formulations of first-order logic often include a concept of type, similar to that found in programming languages. Then every term and subterm has a type, and only type-correct formulas are allowed. Figure 1 presents a first-order formula.

**Figure 1. A puzzle in first-order logic.**

First-order logic has many limitations that curtail its expressiveness. A more expressive alternative is (classical) *higher-order logic.* "Higher-order" means that ∀ and ∃ may range over functions, and functions may be passed as arguments to other functions. Higher-order logic contains pure functional programming (as in F#, Haskell, OCaml, and Standard ML) as a fragment. In particular, functions are represented in curried form: They are passed one argument at a time, and partial applications are allowed. Unlike in most accounts of first-order logic, Booleans are a type, and formulas are simply terms of Boolean type. Predicates are then simply functions that return Booleans.

A very successful computer-oriented approach to theorem proving, which lies at the heart of Zipperposition and many other automatic provers, is to saturate the input problem.

A key feature of higher-order logic is its support for anonymous functions *x* → *f*(*x*) via the syntax (λ*x.* *f*(*x*)). For example, (λ*n.* *n* + 1) maps any integer to its successor. What makes λ so special is that it is automatically evaluated when given an argument; for example, passing the argument k to the function (λ*n. n* + 1) yields the term k + 1. Such implicit conversions are very convenient, but they are also the source of most difficulties when we develop tools based on higher-order logic.

The λ construct is a *binder*, because it introduces a variable that is bound within its body. Other binders can be built on top of λ. For example, you can code the sum as sum(1, *n*, (λ*i.* *g*(*i*))), and similar encodings are possible for the integral and the set comprehension {*x* | *x* > *e*}. With its support for binders, higher-order logic provides a convenient language for doing mathematics.

Figure 2 gives a flavor of higher-order logic by presenting a formulation of Cantor's theorem. The first line defines surjectivity. Notice that the surjective predicate takes a function as argument and that it is defined using a λ. The second line states that there exists no surjective function from any type τ to its powerset, expressed as the function space τ → bool. Higher-order provers can prove this formula automatically.

**Figure 2. Cantor's theorem in higher-order logic.**

### Proving by Saturation

There are many techniques for finding proofs in first- and higher-order logic—some more suitable for humans to use, others for computers. A very successful computer-oriented approach to theorem proving, which lies at the heart of Zipperposition and many other automatic provers, is to *saturate* the input problem. Saturation is a form of proof by contradiction. It consists of three steps:

- Put the negation of the statement to prove
*F*and any necessary hypotheses*H*_{1}, …,*H*in some suitable normal form, yielding a formula set_{n}*F.* - Repeatedly apply inference rules from formulas in
*F*and add the inferences' conclusions to*F.* - Stop if the false formula, denoted by ⊥, is in
*F.*

In other words, a saturation prover starts with a set of formulas and expands it with consequences until ⊥ has been derived. At that point, it has established the implication (*H*_{1} ∧ … ∧ *H*_{n} ∧ ¬*F*) ⇒ ⊥, which is equivalent to (*H*_{1}∧…∧*H*_{n}) ⇒ *F* in classical logic. Compared with other theorem proving methods, an appealing aspect of saturation is that it never needs to backtrack.

With the above procedure, the set of formulas keeps on growing and can quickly explode. Fortunately, the prover may also remove *redundant* formulas from *F.* For example, if *F* contains the formula p, the weaker formula p ∨ q(a) might be considered redundant and removed.

Saturation is a framework that can be used in tandem with many proof calculi. To use it, we need to specify the normal form of our formulas, the inference rules, and ideally rules to remove redundant formulas.

The archetypical example of a saturating proof calculus is first-order *resolution*, introduced by Alan Robinson in 1965.^{22} Resolution provers first put the problem into clausal normal form—a big conjunction of disjunctions:

The quantifiers ∀ and ∃ do not appear in this formula; they are eliminated with the help of a technique called Skolemization. Each disjunction *L*_{i1} ∨ … ∨ *L*_{ini} is called a *clause.* Each component *L _{ij}* is called a

*literal*and has the form either p(

*a*

_{1}, ···,

*a*) or ¬p(

_{n}*a*

_{1}, …,

*a*

_{n}), written p or ¬p if

*n*= 0. The order of literals in a clause is immaterial; thus, p(a) ∨ ¬q and ¬q ∨ p(a) are the same clause. In addition, a clause is allowed to have no literals at all. This empty clause is false. Thus we denote it by ⊥.

A resolution prover is an instance of a saturating prover. Clauses take the role of formulas in the saturation framework described above. The main inference rule is called resolution. If we forget for a moment that clauses may contain variables, the inference rule can be presented in this way:

There is a lot to explain here:

- The label on the right, RES, is the rule's short name.
- The inference rule takes two premises, displayed above the horizontal bar. The premises must be present in the set
*F*for the inference to be applicable. - The inference rule produces a conclusion, displayed below the horizontal bar. This formula gets added to
*F*when the inference is performed. - The notation
*D*∨*L*stands for an arbitrary clause that contains a literal*L*and all the literals from*D.*Similarly,*C*∨ ¬*L*stands for an arbitrary clause that contains the negation of*L*as a literal and all the literals from*C.* - Finally,
*D*∨*C*denotes the clause obtained by combining the literals from*D*and*C.*

The following instance of RES shows the rule in action:

Notice how q and ¬q cancel each other out. An interesting special case of the rule arises when *D* and *C* are the empty clause:

If the formula set *F* contains both the clauses *L* and ¬*L*, then *F* is inconsistent, and RES can be used to derive ⊥, thereby completing the proof by contradiction. Having accomplished its mission, the prover then stops.

The resolution calculus enjoys two desirable properties for a proof calculus. First, it is *sound.* This means that the conclusion of an inference is always a logical consequence of the premises. It is easy to convince ourselves that RES is sound.^{a} The other desirable property is *completeness*, meaning: If the set *F* is inconsistent, then saturation with the resolution calculus will eventually derive ⊥, as long as inferences are performed fairly. Putting all of this together, we get:

Given enough resources, a resolution prover will find a proof if and only if the input problem is provable.

Completeness is much more difficult to establish than soundness, and it is also a less important property in practice. Still, it is reassuring to know that our prover has no blind spots. As an analogy, suppose you are part of a party looking for a treasure on an island. You should make sure that you stay on the island (soundness) and that you explore every square inch of it (completeness).

Figure 3 presents a saturation starting with an inconsistent clause set—clearly, if ¬p and ¬q(a) are true, then p ∨ q(a) is false. The saturation predictably ends with the derivation of the empty clause. The figure's sets capture the consecutive states of *F* in the saturation procedure.

**Figure 3. A saturation using the resolution calculus.**

The simple resolution calculus presented above can be improved in two ways to make it more useful. First, the calculus is needlessly explosive. In the example of Figure 3, we arbitrarily chose in step 2 to resolve p ∨ q(a) against ¬q(a), but we could additionally have resolved it against ¬p. This kind of freedom might lead the prover to explore an excessively large search space.

To guard against this, we can fix an *order* on the predicates. The order is designed in such a way that syntactically large terms are considered large by the order as well. For terms of the same size, we can use tie-breakers; for example, we can state that p is smaller than q. Then, we restrict the RES rule so that it applies only if *L* and ¬*L* are larger than any other literal in their respective premises; the literals *L* and ¬*L* are called *maximal.* This can be done without loss of generality. It makes saturation much less explosive and is still sound and complete. This optimized calculus is called *ordered resolution.*^{3}

Although not needed in theory, the order is crucial to obtain good performance in a practical prover. Intuitively, the situation is analogous to when we want to apply a lemma (*H*_{1} ∧ *H*_{2}) ⇒ *F* in a pen-and-paper proof. To retrieve the conclusion *F*, we need to show both *H*_{1} and *H*_{2}. Without loss of generality, we can focus on *H*_{1} first. If we fail at proving *H*_{1}, there is no point in trying to prove *H*_{2}, because we will never manage to use the lemma anyway.

The order not only breaks symmetries in the search space, it also gives the calculus a sense of direction. The calculus tends to work on the syntactically largest part of a clause and to produce smaller clauses, working its way toward the smallest clause possible: the empty clause.

Next to the order, another improvement to resolution concerns variables. Our RES rule assumes that the problem contains no variables, but for variable-free problems, resolution competes with Boolean satisfiability solvers,^{19} which are much better suited for the task. The true strength of resolution lies in its handling of variables. Like in mathematics, these are understood to be ∀-quantified. Thus, assuming that the constants a and b and the unary function f are declared, a clause such as p(*x*) ∨ q(*x*), where *x* is a variable, represents an infinite set of variable-free clauses

where *x* is instantiated with all possible terms that can be built from the declared functions and constants.

Robinson realized that, following this interpretation of variables, the RES rule can be generalized to allow inferences such as

The inference instantiates *x* with a and *y* with b to make the two predicates p(a,*y*) and p(*x*, b) identical.

The process of computing an assignment for the variables that makes two expressions identical is called *unification.* First-order logic enjoys the nice property that if two expressions are unifiable, there exists a variable assignment that captures that fact in the most general manner possible. This assignment is called the *most general unifier.* Probably Robinson's most celebrated contribution to computer science is an algorithm that decides whether two expressions are unifiable and that computes the most general unifier if it exists.

### Reasoning about Equality

The ordered resolution calculus based on unification is sound and complete for a basic version of first-order logic that does not include equality. For many applications, however, we do need to reason about equality. Since resolution does not know about equality, we must specify its properties explicitly. First, we state that equality is reflexive, symmetric, and transitive:

reflexivity: ∀*x*. *x* = *x*

symmetry: ∀*x*, *y*. *x* = *y* ⇒ *y* = *x*

transitivity: ∀*x*, *y*, *z*. (*x* = *y* ∧ *y* = *z*) ⇒ *x* = *z*

In addition, we state that we can replace equals with equals in function arguments, a property called *congruence.* For example, ∀*x*, *y*. *x* = *y* ⇒ f(x) = f(y). We need to add formulas like this for every function f and for every predicate p as well. Specifying equality in this way is inefficient because the great number of formulas needed to describe it gives rise to lots of unnecessary resolution inferences, making it harder to find a contradiction.

The *superposition* calculus, first described in its entirety by Bachmair and Ganzinger in 1994,^{2} generalizes resolution to reason about equality efficiently with inference rules specifically tailored to this predicate. Once we have equality, other predicates p are not necessary; they can be encoded as functions returning the Boolean values true or false. Accordingly, literals are either equalities *s* = *t* or disequalities *s* ≠ *t.* To establish *symmetry* without even introducing an additional formula or inference rule, we consider *s* = *t* to be the same literal as *t* = *s* and *s* ≠ *t* to be the same literal as *t* ≠ *s.*

The superposition calculus generalizes resolution to reason about equality efficiently with inference rules specifically tailored to this predicate.

The two main rules of the superposition calculus are the superposition rule SUP and the equality resolution rule EQRES. In a simplified form, they can be stated as follows:

The SUP rule is reminiscent of RES. The right premise contains a literal *s*[*t*] ≠ *s'* and possibly some other literals *C.* The notation *s*[*t*] stands for a term *s* that contains *t* as a subterm. If we assume for a moment that there are no extra literals *D* and *C*, the left premise is an equation *t* = *t'* that we use to replace *t* by *t'* in the right premise *s*[*t*] ≠ *s'.* In essence, we replace equals by equals, thus establishing *transitivity* and *congruence.* The extra literals *D* and *C* encode some conditions under which the equation and the disequation hold—for example, "*D* ∨ *t* = *t'*" can be read as "If *D* is false, then *t* = *t'.*" Adding the literals from *D* and *C* to the conclusion is thus necessary to make the rule sound. We have only shown the variant for disequations above, but in its full generality, SUP also allows replacing terms in premises of the form *C* ∨ *s*[*t*] = *s*'.

The rule EQRES allows us to remove any literal of the form *s* ≠ *s* because such a literal is clearly false and therefore it has no impact on the truth of the clause. This rule establishes *reflexivity.*

Like ordered resolution, superposition uses an order to prune the search space, working on larger literals first. In addition, SUP is restricted so that *t* and *s*[*t*] must correspond to the larger sides of equations and disequations, and it replaces larger terms by smaller terms. Superposition is sound and complete.

To illustrate the superposition calculus, we will use it to prove the following lemma:

In ordinary mathematical notation, we would write: "Assuming that *x*^{−1} = 1/*x* for all *x* ≠ 0 and that π ≠ 0, we have |π^{−1}|=|1/π|."

Negating and clausifying yields the following clauses:

In each clause, underlining indicates the maximal sides of the maximal literals according to a reasonable order. In our examples, maximal simply means syntactically largest. If we take *x* in clause (1) to be pi, the underlined term in (1) matches a subterm of the underlined term in clause (3). Thus, we can apply SUP using as premises the instance

of clause (1) together with clause (3) to obtain

Next, we apply EQRES to clause (4) to generate

Now that we have eliminated the larger literal of (4), we may work on the remaining smaller literal. There are multiple SUP inferences possible—for example, between clauses (5) and (3) or between (5) and (4). The inference that leads to the desired contradiction, however, is a SUP inference between clauses (5) and (2) that produces

If the prover is fair, it will eventually perform this inference. Which inferences should be prioritized is an important heuristic choice in practice; this is one of the factors that distinguish good from bad provers. Finally, an EQRES inference on clause (6) yields the empty clause, which proves that the original lemma holds.

### Lost in Translation

Resolution and superposition target first-order logic. First-order provers work well on first-order problems, but most proof assistants are higher order. The gap between the two logics is bridged by tools called *hammers.*^{9}

When users of a proof assistant want to prove a formula, they can develop a detailed proof using the proof assistant's language, or they can invoke a hammer to dispatch the formula to automatic provers. The hammer (1) heuristically selects suitable lemmas from the thousands available, (2) translates them to first-order logic along with the formula to prove, and (3) imports any found proof back into the proof assistant.

Resolution and superposition target first-order logic. First-order provers work well on first-order problems, but most proof assistants are higher order.

Unfortunately, in practice, a lot is lost in step (2). The translation of higher-order constructs is convoluted and leads to poor performance. Usually, hammers will succeed if the original problem does not use any higher-order features, but they will almost always fail if some higher-order reasoning is needed.

Consider the simple formula

from the introduction. In higher-order logic, the formula can be proved by rewriting the left-hand side with the distributivity rule

to obtain , followed by a second rewrite step to produce the desired right-hand side. In a first-order setting, the λ's underlying the Σ expressions must be encoded. A complete translation scheme is based on so-called *combinators.* Following this scheme, the formula to prove is translated to the bulky first-order equation

where app(*f*, *x*) applies an encoded curried function *f* to an argument *x.* The combinators B, C, K, and S are characterized by equations—for example, app(S(*f*, *g*), *x*) = app(app(*f*, *x*), app(*g*, *x*)) for S. This approach produces a lot of clutter. The provers need to do extensive reasoning about the combinators just to determine whether an equation is applicable. As a result, hammers fail to prove the formula of interest in a reasonable time in practice, let alone more difficult formulas.

The solution is to adapt the provers and their underlying calculi to understand higher-order logic directly, thus avoiding translation altogether. However, going native is easier said than done.

### Higher-Order Challenges

Higher-order logic is inherently more complex than first-order logic. For decades, several aspects of the super-position calculus were considered problematic in a higher-order context, blocking progress:

The order used to compare terms.For the first-order superposition calculus to be complete, the underlying order used to compare terms must meet certain requirements. One of these requirements is that a term occurring as a subterm of another term must be smaller than the surrounding term. For example, the term c must be considered smaller than g(c), which in turn must be considered smaller than f(g(c)). A second requirement on the order is that putting two terms into a surrounding context should not affect how they are oriented. For example, if b is larger than a, then f(b, c) must be larger than f(a, c); adding the same context "f(…, c)" to both terms should not affect the order.For higher-order logic, these requirements cannot be met because the implicit reductions of λ's can radically change a term's appearance. For example, by the first requirement, the function (λ

y.f(λz.z)) must be larger than the function (λz.z). If we embed the first function into the context "…(g(f(λz.z)))," the implicit reduction of λ's yields f(λz.z); if we embed the second function into the same context, the reduction yields g(f(λz.z)). The second requirement therefore demands that f(λz.z) be larger than g(f(λz.z)), but the first requirement demands that it be smaller—a contradiction.

Unification of terms.In first-order logic, Robinson's unification algorithm decides whether two terms can be made identical by assigning terms to variables and if so, computes the most general unifier—an assignment that subsumes all other possible assignments. For example, to unify f(x) and f(y), we must setxandyto the same value. Since there are infinitely many possible terms, there are infinitely many possible assignments that unify the two terms. However, we can assignytox(orxtoy) to describe all of these assignments in one. This is the most general unifier.In higher-order logic, when two terms are unifiable, a most general unifier does not necessarily exist. For example, to unify

y(f(a)) and f(y(a)), we could setyto any of the following infinitely many terms: (λx.x), (λx. f(x)), (λx. f(f(x))), … After unification, this would give the terms f(a), f(f(a)), f(f(f(a))), …. Unlike the unifiers of f(x) and f(y) above, these unifiers cannot be described using a single assignment that captures all of them and only them; to describe them all, we need a set of assignments. Therefore, the higher-order concept that corresponds to the most general unifier is acomplete set of unifiers: a set of unifiers that subsumes all unifiers.^{20, 21}The example above shows that this set can sometimes be infinite.In addition, even the question of whether two higher-order terms are unifiable at all is undecidable.

^{15,18}So for any algorithm we devise, there will be nonunifiable terms that it cannot determine to be non-unifiable. Instead, the algorithm may run forever.

Handling of Booleans.First-order logic distinguishes between terms, which are non-Boolean expressions, and formulas, which constitute a Boolean skeleton surrounding the terms. This makes conversion into clausal normal form simple: We only need to convert the skeleton.In higher-order logic, Booleans can occur within any term. Expressions such as (if ∃

x.p(x) then a else b) are supported. Booleans can even occur below λ's as in (λx.if p(x) then a else b). For such expressions, the first-order approach of converting all Booleans into clausal form in a preprocessing step is not possible. We cannot eliminate all Boolean terms by preprocessing.

### Going Higher-Order

Facing the above challenges, the automated reasoning community focused on alternatives to superposition. The prevailing orthodoxy was that higher-order logic is very different from first-order logic and hence it must be tackled by different methods. For years, the performance of higher-order provers was disappointing on hammer benchmarks.^{26}

But now there is a new generation of higher-order provers that aim to gracefully generalize their first-order counterparts. They give up the dogma that higher-order logic is fundamentally different from first-order logic. Instead, they regard first-order logic as a fragment of higher-order logic for which we have efficient methods, and they start from that position of strength.

Possibly the most successful of these systems to date is our prover Zipperposition. Its underlying calculus, λ-superposition, provides answers to the challenges outlined above:

The order used to compare terms.As they are, the order requirements of the superposition calculus cannot be achieved in higher-order logic. Ultimately, the order requirements are dictated by the calculus. When the SUP inference operates on a subterm with a context around it, we need the order to behave well with respect to that context. We saw earlier that the order requirements are met for the first-order-style context "f(…, c)" but not for the specifically higher-order context "…(g(f(λz.z)))."The solution is to design the λ-superposition calculus so that it avoids operating in troublesome contexts. For example, if the problem consists of the clauses g = f and g(a) ≠ f(a), it would notice that the context … (a) around g is troublesome and avoid rewriting the g in g(a) into f. By restricting rewriting to first-order-style contexts, we can use similar orders to compare terms as in first-order logic. This addresses the order issue.

However, we seem to have thrown out the baby with the bath water: Given g = f and g(a) ≠ f(a), we are blocked, even though the two clauses are obviously contradictory. The solution is to introduce a new inference rule that transforms the equation g = f into g(

x) = f(x). The new equation can then be used to rewrite g(a) ≠ f(a) into f(a) ≠ f(a), as in first-order logic. In simplified form, the new inference rule—called argument congruence—can be stated as follows:

Unification of terms.As for the inconvenient explosive behavior of higher-order unification, we cannot avoid it and must adapt our prover architecture to cope with it. To deal with the potentially infinite sets of unifiers, we have devised an implementation of the unification algorithm that regularly pauses and returns control to the main program.^{30}The main program may decide to perform inferences or to focus on other unification problems before resuming work on the given unification problem. To ensure completeness, we must be careful not to ignore any inference or unification problem indefinitely. This can be achieved by interweaving the different computations (that is, by dovetailing).

Handling of Booleans.If we do not eliminate Boolean terms by preprocessing, we need to interleave clausification with the main proving procedure to eliminate Booleans lazily. We accomplish this by means of dedicated inference rules that perform clausification steps. This idea is not new; it is present in several higher-order provers and even in some first-order provers. The main difficulty is to find suitable side conditions for the rules (for example, order conditions). The conditions should restrict the rules as much as possible to prevent an explosion of new clauses, but not so much that the calculus becomes incomplete.

Our λ-superposition calculus that implements these ideas is sound and complete, although both claims come with some caveats. Since we have rules for clausification in our calculus, also the elimination of ∀ and ∃ is performed by inference rules. These rules may introduce new constants, called Skolem constants. For example, the term ∃*x.* p(*x*) can be transformed into p(c), where c is a new Skolem constant—if there exists an *x* such that p(*x*), then we may postulate the existence of a c such that p(c). Technically, however, this rule is not strictly speaking sound, because p(c) is not a logical consequence of ∃*x.* p(*x*); after all, ∃*x.* p(*x*) says nothing about *c.* Even so, the Skolem constants cannot introduce a logical contradiction from noncontradictory assumptions, and it is even possible to give them a semantics that actually makes Skolemization sound. This is sufficient for our prover to work correctly.

Regarding completeness, the caveat is that as a consequence of Gödel's first incompleteness theorem,^{13} there exist true statements for which there are no proofs. Naturally, our calculus cannot prove these statements, but nor can traditional higher-order proof systems or proof assistants—these are theorem provers, not truth provers. To avoid this issue, our completeness result is stated with respect not to the standard semantics of higher-order logic, which is subject to the worst consequences of Gödel's incompleteness theorem, but to a weaker notion called Henkin semantics, which considers only those statements to be true that have a proof. Thus, if a problem is *provably* inconsistent according to a traditional notion of provability, our calculus can be used to derive the empty clause ⊥.

To demonstrate the λ-superposition calculus, we will use it to prove the equation

from the introduction. The only axiom we need is the distributivity law

where the variables *f* and *g* range over functions. First, for a proof by contradiction, we negate the formula we want to prove. In addition, we express the sums using λ's. The problem becomes

As before, underlining indicates the maximal sides of the maximal literals according to a reasonable order. If we take *f* to be (λ*x.* *x*^{2}) and *g* to be (λ*x.* 2*x*) in clause (8), the right-hand side of (8) matches the term sum(1, *n*, (λ*i.* *i*^{2})) + sum(1, *n*, (λ*i.* 2*i*)) in clause (7). Here, it is crucial that λ's automatically reduce—for example, instantiating *f* with (λ*x.* *x*^{2}) in (λ*i.* *f*(*i*)) first results in (λ*i.* (λ*x.* *x*^{2})(*i*)) but then reduces to (λ*i.* *i*^{2}). Thus, a SUP inference between clauses (7) and (8) is possible and yields

Next, we need to use clause (8) a second time. If we take *f* to be (λ*x.* *x*^{2} + 2*x*) and *g* to be (λ*x.* 1), the right-hand side of clause (8) matches the right-hand side of clause (9). A SUP inference between clauses (8) and (9) yields

Now both sides are equal, and an EQRES inference yields the empty clause, proving the original equation. This derivation is typical of the superposition calculus: To prove that an equality follows from other equalities, we state it as a dis-equality, we apply SUP inferences on either sides of ≠ until both sides are identical, and finally, we apply EQRES to derive ⊥.

This native approach is fast and direct. In contrast, with the first-order encoding of λ's as combinators discussed above, two SUP inferences would not have sufficed. We would have needed several SUP inferences with the equations characterizing the combinators to get the terms in the negated lemma and the distributivity rule to match. In addition, each SUP inference would have competed with many others that are also applicable. The automatic reduction of λ's is what enables λ-superposition to prove this example equation efficiently. It replaces blind exploration by directed computation.

The Zipperposition prover, which implements λ-superposition, served primarily as an experimentation vehicle. Now that we are convinced of the calculus's value, we have started reimplementing its key ideas in the high-performance E prover.^{23}

### Alternative Approaches

In half a century of native higher-order calculus and prover development, many approaches have been proposed. We briefly review the main ones.

Resolution.Higher-order automated reasoning really took off with Gérard Huet's extension of resolution to higher-order logic.^{14}The key idea was to use higher-order unification, which Huet had to develop as well,^{16}in place of Robinson's first-order unification. The main limitation of higher-order resolution is that it does not natively support equality reasoning. This was added by Christoph Benzmüller and his colleagues in the LEO series of provers: LEO,^{6}LEO-II,^{7}and Leo-III.^{24}

Superposition.Leo-III implements a calculus that is quite similar to an incomplete version of λ-superposition. Its predecessors LEO and LEO-II, on the other hand, did not feature an order to compare terms, leading to many unnecessary inferences. Another related approach consists in using combinators to represent λ-expressions, in combination with a superposition-like calculus. This is the route taken by Ahmed Bhayat and Giles Reger in Vampire.^{8}

Matings.Another approach that has been studied extensively relies on matings, or connections. Peter Andrews's TPS^{1}is based on this approach. The approach translates logical formulas to matrices and looks for paths with certain properties in these matrices. Once the prover successfully closes a path, a contradiction is found. The calculus is comparatively easy to implement, but it does not scale very well, especially in the presence of superfluous axioms.

Tableaux.Roughly speaking, the tableau calculus emulates what a rigorous mathematician would do on paper. It analyzes the formula systematically, building a tree that keeps track of the remaining cases to prove. The Satallax prover^{10}developed by Chad Brown and colleagues implements a higher-order tableau calculus guided by a satisfiability (SAT) solver. Tableaux are simple and intuitive, and they can work directly on unclausified formulas. On the negative side, they can end up repeating work in separate branches of the tree, harming performance, and equality reasoning is not their strong suit. A related approach, called focused sequent calculus, is implemented in Fredrik Lindblad's agsyHOL system.^{17}

Satisfiability modulo theories.Solvers based on satisfiability modulo theories (SMT) have enjoyed a lot of success for verifying hardware and software in the past two decades. Some support full first-order logic, including quantifiers. Among these, the solvers cvc5 and veriT have been extended by Barbosa et al.^{4}to provide some support for higher-order logic. The strength of SMT solvers is their native support for decidable theories, such as linear arithmetic on integers and real numbers. Their main weakness is their handling of quantifiers, for which they rely heavily on trial and error.

### Performance on Benchmarks

Designing a proof calculus that is sound and complete is relatively easy. The real difficulty is to design a calculus that is sound, complete, and efficient. In theorem proving, the proof of the pudding is in the eating. To give a flavor of the performance of the different calculi and provers, we present the results of two empirical evaluations. Table 1 summarizes the results.

**Table 1. Empirical prover comparison.**

The first evaluation is the higher-order theorem division of the CADE ATP System Competition (CASC).^{27} This competition takes place every year at the Conference on Automated Deduction (CADE) or the International Joint Conference on Automated Reasoning (IJCAR). The middle column of Table 1 presents the number of proved problems, out of 500 problems, by each prover that participated in the 2021 edition of CASC.^{28} The problems come from a variety of sources and aim to be representative of the applications of automatic provers. A wall-clock time limit of 120 s per problem was used. Zipperposition won (indicated in bold), and Vampire came in second.

Designing a proof calculus that is sound and complete is relatively easy. The real difficulty is to design a calculus that is sound, complete, and efficient.

The second evaluation is a recent study called Seventeen^{12} by Martin Desharnais, Makarius Wenzel, and two of the present authors. For this study, 5,000 problems were generated based on a proof assistant's library. These problems tend to be larger but use fewer higher-order features than the CASC problems. A CPU time limit of 30s was used. Zipperposition won again against the other higher-order provers, followed by E. All in all, the competition confirms the newly won supremacy of superposition-based approaches.

### Prospects

For many years, higher-order reasoning was something of a fringe topic. Perhaps researchers thought that first-order logic was already sufficiently challenging. In recent years, the picture has changed dramatically with the emergence of higher-order provers based on superposition and SMT. The leading approaches for reasoning about classical first-order logic are finally finding their way into higher-order provers. These provers are integrated in hammers, providing valuable automation to users of proof assistants.

One possible criticism of higher-order provers is that they still automate only what mathematicians would consider very easy or trivial—a far cry from the dream of fully mechanical mathematicians. However, as users of proof assistants know, a lot of time is wasted proving very easy or trivial results. Having little mechanical mathematicians that take care of the easy mathematics means that users can focus on more challenging, and interesting, problems.

We see three main avenues for future work. First, SMT is a very successful technology in the first-order world, and we expect it to catch up with λ-superposition. Second, higher-order logic can express induction principles natively, but so far little work has gone into automating higher-order proofs by induction. Third, several proof assistants, such as Coq and Lean, use a logic more powerful than higher-order logic—called dependent type theory; extending higher-order proof calculi to support this logic would increase proof automation for these systems.

### Acknowledgments

We thank S. Cruanes for allowing us to extend Zipperposition and helping us in the process. We thank the Matryoshka team, including P. Fontaine, S. Merz, and S. Schulz, and the other researchers working on automating higher-order logic, including C. Benzmüller, A. Bhayat, C. Brown, G. Reger, and A. Steen. Finally, we thank A. Baanen, L. Bentkamp, W. Fokkink, V. François-Lavet, V. Hartmann, W. Nawrocki, M. Summerfield, and J. Urban.

The research on λ-superposition has received funding from the European Research Council (ERC) under the European Union's Horizon 2020 research and innovation program (Grant agreement No. 713999, Matryoshka). It has also received funding from the Netherlands Organization for Scientific Research (NWO) under the Vidi program (Project No. 016.Vidi.189.037, Lean Forward). Bentkamp's work on this paper has received funding from a Chinese Academy of Sciences President's International Fellowship for Postdoctoral Researchers (Grant No. 2021PT0015) and from the Natural Science Foundation of China (Grant No. NSFC-61732001).

### References

1. Andrews, P.B., Bishop, M., Issar, S., Nesmith, D., Pfenning, F., Xi, H. TPS: A theorem-proving system for classical type theory. *J. Autom. Reason. 16*, 3 (1996), 321–353.

2. Bachmair, L., Ganzinger, H. Rewrite-based equational theorem proving with selection and simplification. *J. Log. Comput. 4*, 3 (1994), 217–247.

3. Bachmair, L., Ganzinger, H. Resolution theorem proving. In *Handbook of Automated Reasoning, Vol. I*, J.A. Robinson and A. Voronkov, eds. (2001). Elsevier and MIT Press, 19–99.

4. Barbosa, H., Reynolds, A., Ouraoui, D.E., Tinelli, C., Barrett, C.W. Extending SMT solvers to higher-order logic. In *CADE-27 (LNCS, Vol. 11716)*, P. Fontaine, ed., (2019). Springer, 35–54.

5. Bentkamp, A., Blanchette, J., Tourret, S., Vukmirović, P. Superposition for full higher-order logic. In *CADE-28 (LNCS, Vol. 12699)*, A. Platzer, G. Sutcliffe, eds. (2021). Springer, 396–412.

6. Benzmüller, C., Kohlhase, M. Extensional higher-order resolution. In *CADE-15 (LNCS, Vol. 1421)*, C. Kirchner, H. Kirchner, eds. (1998). Springer, 56–71.

7. Benzmüller, C., Sultana, N., Paulson, L.C., Theiss, F. The higher-order prover LEO-II. *J. Autom. Reason. 55*, 4 (2015), 389–404.

8. Bhayat, A., Reger, G. A combinator-based superposition calculus for higher-order logic. In *IJCAR 2020, Part I (LNCS, Vol. 12166)*, N. Peltier, V. Sofronie-Stokkermans, eds. (2020). Springer, 278–296.

9. Blanchette, J.C., Kaliszyk, C., Paulson, L.C., Urban, J. Hammering towards QED. *J. Formaliz. Reason. 9*, 1 (2016), 101–148.

10. Brown, C.E. Satallax: An automatic higher-order prover. In *IJCAR 2012 (LNCS, Vol. 7364)*, B. Gramlich, D. Miller, U. Sattler, eds. (2012). Springer, 111–117.

11. Church, A. A note on the Entscheidungsproblem. *J. Symb. Logic 1*, 1 (1936), 40–41.

12. Desharnais, M., Vukmirović, P., Blanchette, J., Wenzel, M. Seventeen provers under the hammer. In *ITP 2022 (LIPIcs, Vol. 237)*, J. Andronick, L. de Moura, eds. (2022). Schloss Dagstuhl—Leibniz-Zentrum für Informatik, 8:1–8:18.

13. Gödel, K. Über formal unentscheidbare Sätze der Principia Mathematica und verwandter Systeme I. *Monatshefte für Mathematik und Physik 38*, 1 (1931), 173–198.

14. Huet, G.P. A mechanization of type theory. In *IJCAI-73*, N.J. Nilsson, ed. (1973). William Kaufmann, 139–146.

15. Huet, G.P. The undecidability of unification in third order logic. *Inf. Control. 22*, 3 (1973), 257–267.

16. Huet, G.P. A unification algorithm for typed lambda-calculus. *Theor. Comput. Sci. 1*, 1 (1975), 27–57.

17. Lindblad, F. A focused sequent calculus for higher-order logic. In *IJCAR 2014 (LNCS, Vol. 8562)*, S. Demri, D. Kapur, C. Weidenbach, eds. (2014). Springer, 61–75.

18. Lucchesi, C.L. The undecidability of the unification problem for third order languages. *Report CSRR 2059* (1972), 129–198.

19. Malik, S., Zhang, L. Boolean satisfiability: From theoretical hardness to practical success. *Commun. ACM 52*, 8 (2009), 76–82.

20. Pietrzykowski, T. A complete mechanization of second-order type theory. *JACM 20*, 2 (1973), 333–364.

21. Plotkin, G. Building-in equational theories. *Mach. Intell. 7* (1972), 73–90.

22. Robinson, J.A. A machine-oriented logic based on the resolution principle. *J. ACM 12*, 1 (1965), 23–41.

23. Schulz, S., Cruanes, S., Vukmirović, P. Faster, higher, stronger: E 2.3. In *CADE-27 (LNCS, Vol. 11716)*, P. Fontaine, ed. (2019). Springer, 495–507.

24. Steen, A., Benzmüller, C. The higher-order prover Leo-III. In *IJCAR 2018 (LNCS, Vol. 10900)*, D. Galmiche, S. Schulz, R. Sebastiani, eds. (2018). Springer, 108–116.

25. Stroustrup, B. *The Design and Evolution of C++.* Addison-Wesley, 1995.

26. Sultana, N., Blanchette, J.C., Paulson, L.C. LEO-II and Satallax on the Sledgehammer test bench. *J. Appl. Logic 11*, 1 (2013), 91–102.

27. Sutcliffe, G. The CADE ATP System Competition—CASC. *AI Mag. 37*, 2 (2016), 99–101.

28. Sutcliffe, G., Desharnais, M. The CADE-28 Automated Theorem Proving System Competition—CASC-28. *AI Commun. 34*, 4 (2022), 259–276.

29. Turing, A.M. On computable numbers, with an application to the Entscheidungsproblem. *Proc. London Math. Soc. s2-42*, 1 (1937), 230–265.

30. Vukmirović; , P., Bentkamp, A., Blanchette, J., Cruanes, S., Nummelin, V., Tourret, S. Making higher-order superposition work. In *CADE-28 (LNCS, Vol. 12699)*, A. Platzer, G. Sutcliffe, eds. (2021). Springer, 415–432.

31. Vukmirović, P., Blanchette, J., Cruanes, S., Schulz, S. Extending a brainiac prover to lambda-free higher-order logic. Int. J. Softw. Tools Technol. Transf. 24, 1 (2022), 67–87.

### Footnotes

a. The justification for the general rule is as follows: Either *L* or ¬*L* is true. If *L* is true, then ¬*L* is false, and therefore, the rest of the second premise, *C*, must be true. A fortiori, *D* ∨ *C* must be true. Similarly, if ¬*L* is true, then *L* is false and therefore *D* and a fortiori *D* ∨ *C* must be true.

Copyright held by authors/owners. Publications rights licensed to ACM.

Request permission to publish from [email protected]

The Digital Library is published by the Association for Computing Machinery. Copyright © 2023 ACM, Inc.