1 Two views of Proof: history of the question

Avigad’s paper adds to a debate that can be traced to the origins of modern mathematics in the early twentieth century. The historic division is between those like HilbertFootnote 1 and the BourbakistsFootnote 2 who wished to drive the modern tendency towards ever more formal and abstract mathematics to its limit, and those like PoincaréFootnote 3 and BrouwerFootnote 4 who thought (in different ways) that mathematics ineliminably refers to human experience and activity, and therefore judged that complete formalisation is either unwise or impossible. This broad contrast developed into a debate over (what we now call) the Standard View: that full formalisability is not merely a splendid and valuable feature of mathematical proofs, but is a criterion or norm of rigour. For example, Saunders Mac Lane claimed that, “In practice, a proof is a sketch, in sufficient detail to make possible a routine translation of this sketch into a formal proof” and that, “…the test for the correctness of a proposed proof is by formal criteria and not by reference to the subject matter at issue” (1986 pp. 377-8). Here is a looser statement from Thomas Hales,

The ultimate standard of proof is a formal proof, which is nothing other than an unbroken chain of logical inferences from an explicit set of axioms. While this may be the mathematical ideal of proof, actual mathematical practice generally deviates significantly from the ideal. (2012, p. x)

Where Mac Lane describes the informal proof as a ‘sketch’, Hales writes (in the title of his book) of a ‘blueprint’. Solomon Feferman, at the end of his (2012), sought to specify the relation between an informal proof and a corresponding formal derivation without using such metaphors:

...the Formalizability Thesis should be given a very strict reading, namely that (i) every good proof has an underlying logical structure, (ii) that structure is completely analyzed in the derivation that formalizes the proof, and, finally (iii) that derivation assures the correctness of the theorem proved on the basis of the background assumptions expressed by the axioms and rules of the system in which the proof is formalized.

For a more recent expression of the idea that proof is really about syntax, here is Joel D. Hamkins,

Proof and truth… lie on opposite sides of the syntax-semantics divide, for at bottom, a proof is a kind of argument, a collection of assertations structured syntactically in some way, while the truth of an assertion is grounded in deeply semantic issues concerning the way things are… Proof… lies solidly on the syntactic side, since ideally one can verify and analyze a proof as a purely syntactic object, without a concept of meaning and without ever interpreting the language in any model. (2020, pp. 157-8)

In fairness, it should be noted that this quotation comes from an introductory lecture series in which Hamkins outlines a range of perspectives and leaves the deeper questions that they raise for students to discuss. Nonetheless, these examples are enough to show why this is called ‘the Standard View’. It occurs in mathematicians’ discussions of proof, often with little or no supporting argument, as if it were an unobjectionable statement of what all mathematicians mean by ‘proof’. It is almost always joined with a recognition that reality rarely approaches this ideal (as in Mac Lane and Hales, just quoted). Here is Hamkins, a few pages on: “Most contemporary mathematical proofs are written in prose, essay-style… In mathematical practice, a proof is any sufficiently detailed convincing mathematical argument that logically establishes the truth of a theorem from its premises.” (p. 160). Students might wonder how prose, even mathematical prose, can ‘lie solidly on the syntactic side’. In most of these presentations, the tension between the ideal of a purely syntactic object and the reality of proofs written in semantically rich prose is either shrugged off or set aside with a claim (as in Mac Lane) that the translation between informal proof and formal derivation is ‘routine’ or otherwise unproblematic. Of course, some aspects of mathematical argumentation are perfectly well modelled by formal logic. Every proof by contradiction, for example, is a clear, undisguised case of reductio ad absurdum.

Some mathematicians do worry about in the relation between an informal proof and its corresponding derivations,Footnote 5 such as Hersh (1997) and most notably Rav (1999). Rav asked why we prove theorems, and his answers all turned on a claim that proofs include ‘topic-specific moves’ (p. 26) that cannot be re-cast in formal logic without loss or violence. This is also a central point for Hersh, “The passage from informal to formalized theory must entail loss of meaning or change of meaning” (1997, p. 160). Mac Lane, in contrast, claims that if an informal proof is rigorous, this translation must be ‘routine’ and that the test for correctness should made no reference to the subject matter, that is, should not be topic-specific (quoted above).

Thus, we have some mathematicians (Hersh, Rav) insisting that informal proofs are often so different from formal derivations that the latter have little relevance to the business of writing and checking the former. Other mathematicians (Mac Lane, Feferman, perhaps Hales and Hamkins) sail close to claiming that a rigorous informal proof in some sense is a formal derivation (‘at bottom’, under ‘complete analysis’ or up to ‘routine’ translation). What, in this circumstance, is a philosopher to do? One of the most widely discussed accounts of the matter is Jody Azzouni’s (2004)Footnote 6 ‘derivation-indicator’ view.

Azzouni, seeking to specify a role for formal derivations while doing justice to the rich descriptions of proof-practice that he found in Rav and others, argued that an informal proof is not a formal derivation somehow abbreviated or disguised. Rather, a valid informal proof indicates the existence of a formal derivation and in this way meets the norm of formal correctness. Azzouni later modified this view (2009), giving up the phrase ‘derivation-indicator’ in favour of talk of topic-specific inference packages that sound rather like Rav’s topic-specific moves. In spite of this partial rapprochement, there are some important differences between Azzouni’s eventual position and Rav’s outlook. Azzouni works hard in his (2009) paper to identify the role that formal logic has in informal proof practice (see his discussion of ‘content containment’), and he ties his account to human cognitive processes and capacities, whereas Rav talks about topic-specific mathematical moves that might in principle be carried out by a cephalopod or an alien.

Azzouni’s chief motive for giving up the derivation-indicator view seems to be that he found himself explaining observable, measurable social facts—the reliability and stability of mathematical knowledge, the confidence of mathematicians in their results and the high degree of consensus in the mathematical research community—by reference to something that in almost all cases is non-existent:

I kept falling (against my will) into a view that mathematicians had to be engaged in something like sophisticated syntactic pattern-recognition while perusing informal mathematical proofs, so that they would be sensitive (without realizing it) to a background of nonexistent formal derivations.Footnote 7

Philosophers of the Rav tendency often rely on some version of this point. Formal derivations corresponding to informal proofs almost never exist in material reality. They might be posited in principle, and sometimes the structure of the informal proof might suggest a map of how a derivation could be worked up. Nevertheless, the posited formal derivations almost always remain materially non-existent and therefore ineligible to be elements in the causal history of a psychological or social fact. Whatever job it is that formal derivations are supposed to do in mathematical practice, they somehow must be able to do it without existing.Footnote 8

There are two more points to make about this debate before turning to Avigad’s recent paper. First, practicing mathematicians supply the contending philosophical positions. The fact that mathematicians feel moved to say what they do is part of the data for philosophers of mathematical practice. In particular, philosophers who favour Rav’s outlook need to explain why mathematicians so often announce some version of the Standard View. It matters, even if it is strictly false.Footnote 9 The philosopher’s work would not yet be complete if one side of this debate triumphed over the other, because (whichever way it went), all the data must be accounted for, including the reflections of mathematicians committed to the defeated view.

Second, notice how Azzouni got drawn (against his will) into making a claim in philosophy of mind. The thought that informal proofs are really (‘at bottom’, after ‘routine’ translation) syntactic items leads naturally to the idea that in reading them, mathematicians are doing some sort of syntactic processing. This is a special case of the idea that all human thinking is syntactic processing, in spite of appearances. That general idea owes some of its grip on the contemporary philosophical imagination to the omnipresence of digital devices, which now carry out tasks that look as if they belong solidly on the semantic side, but which are at bottom (at the level of machine-code), syntactic processes. In addition, the brain-as-computer idea has a role in cognitive science because it helps researchers to ask precise questions (about, for example, memory size and structure). It may be also true, but results in experimental psychology suggest otherwise (Kahneman, 2012). None of the authors cited in this paper have committed themselves to computationalism in the philosophy of mind. Nevertheless, that is the direction in which these arguments point.

To summarise: there is a tension in the Standard View arising from the differences between the ideal of a wholly syntactic proof and the reality of informal proofs written essay-style in prose. Attempts to resolve this tension pull philosophers and mathematicians towards claiming that informal proofs are, in spite of appearances, not really informal. To a philosopher feeling this tension, informal proofs can come to look like formal derivations in disguise, their underlying syntactic nature waiting to be revealed by translation or analysis. From here, it is a short step to claiming that when mathematicians read informal proofs they are really engaging in syntactic processing. With that step taken, the philosopher of mathematics who began by trying to articulate the Standard View then stands on the brink of making a commitment in the long-standing debate about whether the human brain works like a digital computer. There may be an independent argument for the brain-as-computer thesis, but it lies outside the philosophy of mathematical practice.

2 Avigad, J. [2020] reliability of Mathematical Inference

The abstract of Avigad’s paper reads as follows:

Of all the demands that mathematics imposes on its practitioners, one of the most fundamental is that proofs ought to be correct. It has been common since the turn of the twentieth century to take correctness to be underwritten by the existence of formal derivations in a suitable axiomatic foundation, but then it is hard to see how this normative standard can be met, given the differences between informal proofs and formal derivations, and given the inherent fragility and complexity of the latter. This essay describes some of the ways that mathematical practice makes it possible to reliably and robustly meet the formal standard, preserving the standard normative account while doing justice to epistemically important features of informal mathematical justification.

The first thing to note is that what we might call the ‘observational core’ of his argument—his partial natural history of strategies for constructing sound informal proofs (Sects. 3 and 4 of his paper)—is a significant and insightful contribution to the philosophy of mathematical practice, and will remain so regardless of the fate of his larger argument.

To begin, consider Avigad’s gloss on the Standard View:

According to the standard view, a mathematical statement is a theorem if and only if there is a formal derivation of that statement, or, more precisely, a suitable formal rendering thereof. When a mathematical referee certifies a mathematical result, then, whether or not the referee recognizes it, the correctness of the judgement stands or falls with the existence of such a formal derivation. (2020, p. 4)

It matters to what follows to get the modalities of this statement right. Avigad is not simply saying that wherever there is a sound informal proof, there is as a matter of fact the possibility-in-principle of writing a corresponding formal derivation. If that were the whole of the Standard View, there would be little discussion because, as he points out, long-running programmes in the foundations of mathematics give us compelling reasons to think that every sound informal proof can in principle be supplied with a correct formal correlate, and what is more there is a growing library of formal derivations of significant theorems. Avigad’s claim is something stronger: correspondence with a formal derivation is the very meaning of correctness for an informal proof. Throughout his paper, he uses Azzouni’s formulation that the existence of a derivation is the ‘normative standard’ for the correctness of an informal proof. He rejects Detlefsen’s (2008) suggestion that ‘[informal] rigor and formalization are independent concerns’, on the grounds that it ‘requires us to provide an independent characterization of rigor and provide some other explanation of what it means for an informal proof to be correct.’ (2020, p. 6). It is evident from the dialectical context that he does not expect this challenge to be met. On the other hand, he says nothing here about the relation between the informal proof and its corresponding derivations (unlike Mac Lane’s insistence that the translation between them must be ‘routine’ or Feferman’s requirement that the derivation is the logical analysis of the informal proof).

The chief obstacle for the Standard View, according to Avigad, is to explain how informal proofs—long, complex and difficult as they may be—can be the sort of things that entail the existence of formal derivations. To meet this challenge, he deploys the observational core of his argument. Part of his answer is that informal proofs (unlike formal derivations) do not have to be wholly error-free—an informal proof can play its epistemic and logical roles even if it has small, easily fixed errors, mistakes in book-keeping, mislabelling and the like (2020, p. 7). This robustness is in part due to the stabilising role of the skilled mathematical reader, who can see the mistakes and figure out what ought to have been printed. Avigad proceeds to develop the beginnings of a natural history of desirable proof-features. He observes that proofs are modular—they divide into chunks that prove lemmas, and the chunks can be passed around from proof to proof, so a new proof may rely on some previously established modular parts that have already shown their reliability, and new modular parts can be checked in isolation from the rest of the proof. Inferences in proofs are motivated—a move in a proof is intelligible because it plays some part in the overall proof strategy, which makes them easier for the reader to grasp. Avigad suggests three general strategies for writing robust proofs:

  • Isolate and minimize critical information.

  • Maximize exposure to error detection.

  • Leverage redundancy.

The working-through of a proof may involve a lot of standard moves, and a proof written for robustness will downplay this familiar material in order to foreground whatever is novel or unique, so that readers can focus on it and interrogate it. The second point means building in checks so that an error will show up vividly. Finally, the robustness of informal proofs depends in part on the fact that there are often many different ways of proving the same lemma or result. Avigad then suggests a non-exhaustive list of some more specific heuristics:

  1. 1.

    Reason by analogy.

  2. 2.

    Modularize.

  3. 3.

    Generalize.

  4. 4.

    Use algebraic abstraction.

  5. 5.

    Collect examples.

  6. 6.

    Classify.

  7. 7.

    Develop complementary approaches.

  8. 8.

    Visualize.

The analogies Avigad has in mind can be between structures (say between the integers and the Gaussian integers), or arguments, or construction heuristics like embedding a class of objects into a bigger structure with more tractable properties. By ‘algebraic abstraction’, Avigad means capturing the mathematically important features of a structure in axioms, such as the group axioms. These heuristics can support each other. For example, collecting examples is an obvious precursor to classification, but a classification can be more powerful if it is ordered according to some structural feature, and this feature may be a candidate for capture in axioms, and so become a case of algebraic abstraction.Footnote 10 Avigad supplies examples and discussion that I will not reproduce here because I have nothing critical or novel to say about the detail of what I am calling the ‘observational core’ of his paper.Footnote 11 Note, though, that these strategies all depend to some degree on the mathematics being meaningful to human mathematicians. Some (such as 2 and 4) carry over to formal derivations relatively smoothly. Others, such as 8, do not. Curiously, Avigad does not explore the extent to which these strategies for informal proofs do or do not tend to produce proofs that map easily (‘routinely’) across to formal derivations. On the contrary, he presents these strategies as means for managing logical relations internal to the informal proof. They are not about building connections between the informal proof and a corresponding formal derivation.Footnote 12 They are about making sure that the informal proof works in its own terms.

This is why the observational core of Avigad’s paper could just as well have been written by someone building on the views of Yehuda Rav or Michael Detlefsen, that is to say, the claim that the rigour of informal proofs can (on the whole, in most cases) be accounted for without reference to formal derivations. Avigad’s analysis does not directly explain how informal proofs meet the standard of correctness set out in the Standard View. His analysis cannot do that because it does not mention formal derivations at all. Rather, it explains (or at least, begins to explain) how it is that informal proofs can be truth-preserving. In doing so, it indirectly helps us to understand how they meet the formalisability norm set out in Avigad’s reading of the Standard View—but only because results in the foundations of mathematics tell us that a sound informal proof will be formalisable. Informal mathematical proofs are highly truth-preserving in part because they isolate critical information, expose themselves to error detection, leverage redundancy, and so on through the rest of Avigad’s good heuristic advice. The observational core of Avigad’s paper can be adopted wholesale by critics of the Standard View, because it says nothing about the alleged relation between informal proofs and formal derivations. Apart from a few references to a paper by Hamami (2019), Avigad’s heuristic observations are entirely about informal proofs alone, not about their relation to derivations. The indifference of Avigad’s heuristics to formal derivations rather supports the thought that the practically effective norm for mathematical proofs is that they should be sound.

That said, the challenge that Avigad presents to the Rav tendency remains, namely, to provide some alternative account of the correctness of informal proofs. After all, most of Avigad’s heuristics would be good advice for legal or historical argument (slot in sub-arguments that have already been well tested, find multiple arguments for the same conclusion, etc.) and almost all of it is good advice for philosophers (collect examples, classify, identify abstract principles, etc.). The challenge for the Rav tendency is to explain how informal proofs attain mathematical levels of reliability, and this cannot be achieved by only pointing to general heuristics of this sort. Some in the Rav tendency have proposals, but testing them is not the aim of the present paper.Footnote 13 Proponents of the strongest version of the Standard View—that sound informal proofs are formal derivations in disguise—can turn to formal logic to explain how proofs work, but do have to make their core thesis plausible in the face of Avigad’s worry about fragility, Azzouni’s worry about how mathematicians engage with derivations and fact that informal proofs and derivations look different and seem to work differently. Someone who wishes to defend the Standard View without claiming that informal proofs are only superficially informal would face the same challenge as the Rav tendency. If we allow that informal proofs are not merely syntactic objects disguised in human language, then the challenge that Avigad presents to the Rav tendency is the very problem that he addresses in his paper. I will argue in the next section that Avigad equivocates between these two versions of the Standard View.

This completes the case for the first claim of this paper: that the observational core of heuristic advice in Avigad’s paper is entirely agnostic between rival accounts of mathematical correctness.

3 The syntactic side of the tension

I now move to the second claim of this paper, that the tension at the heart of the Standard View is still there in Avigad’s version and sometimes pushes him towards radical theses in philosophy of mind. Recall how that temptation goes: informal proofs and formal derivations often look quite different, and in any case the formal derivation corresponding to a proof is almost never produced. Nevertheless, according to the Standard View, the existence of formal derivations is somehow normative for informal proofs. A tempting resolution is to argue that in spite of appearances, the informal proof is really a derivation in disguise. Then, two problems for the Standard View—the non-existence of derivations and their apparent difference in kind from informal proofs—both disappear. In that case, ‘routine’ translation and faithful logical analysis do not transform a proof but merely reveal its essence. Once this line has been taken, it is natural to adopt a computational view of the mathematical mind. Since mathematicians are humans, a general computationalism in the philosophy of mind beckons.

As we saw, Avigad’s characterisation of the Standard View does not describe the relation between informal proofs and formal derivations, but he does offer some clues in the body of his paper. Near the start of his paper, Avigad adopts the familiar image of informal proofs as sketches, and Azzouni’s language of derivation indication:

On the standard view, [informal proofs] are only high-level sketches that are intended to indicate the existence of formal derivations. But providing less information only exacerbates the problem… (2020, p. 4)

Avigad does not unpack the sketch analogy, but he does recommend Yacin Hamami’s (2019) which does exactly that.Footnote 14 Echoing Mac Lane, Hamami writes: ‘a mathematical proof is rigorous if and only if it can be routinely translated into a formal proof.’Footnote 15 The central part of Hamami’s paper is a careful specification what he thinks ‘routine translation’ has to mean for the Standard View to be cogent:

…the notion of translation in the standard view is quite different from the one of linguistic translation. …a better analogy would be with the process of compilation, that is, with the ‘translation’ of a computer program written in a high-level programming language into machine language.Footnote 16

Hamami distinguishes four levels of ‘code’ linked by three stages of ‘compilation’. The essential point is that on his view (which Avigad sometimes suggests he shares), the ‘routine translation’ of informal proof into formal derivation that the Standard View requires is not like translating a meaningful text from one human language to another. It is, rather, like the use of syntactic substitutions to move from a high-level computer language where a programmer can call an arbitrarily large and complex subroutine with a single command down to the level just above the firmware. ‘Routine’ here does not mean ‘easy for humans’ or even ‘feasible for humans’. It means that a digital machine could do it. It also means that, layers of compilation and syntactic abbreviation notwithstanding, informal proofs and formal derivations are essentially the same sort of thing. In other words, in Hamami (though not directly in Avigad), we find the strong version of the Standard View, that sound informal proofs are syntactic items in disguise.

Avigad offers some other analogies in the same vein:

…an informal proof is a form of data compression. Coding schemes for data represent the most common patterns concisely, reserving extra bits for those that are unusual and unexpected. To invoke another analogy, software developers use version control software to store a project’s history in a shared repository. To save space, the repository only has to store the difference between successive versions, rather than a new copy.

As in Hamami, the difference between the informal proof and the formal derivation is really just a process of selective abbreviation. They are both syntactic objects—it’s just that the formal derivation is much longer because it is expressed in a foundational system (usually taken to be a combination of set theory and classical logic). In these data compression and software development analogies, Avigad seems to commit himself to the strong version of the Standard View, that informal proofs are syntactic objects in disguise. However, Avigad does not always follow this line.

4 The semantic side of the Tension

The claim of the present paper is that the tension in the Standard View is there in Avigad’s article as it was in Mac Lane, Azzouni, and the other authors we canvassed above. The Standard View looks implausible because most informal proofs do not seem to work like purely syntactic objects, even though mathematical notation may make them look like syntactic objects. Like other kinds of reason-giving and argument-making, informal mathematical proofs depend on communities of practitioners sharing a common understanding of what moves are permitted within the practice, in virtue of their grasp of the nature of the subject-matter. Mathematicians have some advantages over other communities of reasoners. They can offload some of their thinking to highly efficient notational systems that partially encode the rigour of the practice. Ordinary high-school algebraic notation can serve an example of this: its introduction in the early seventeenth century massively extended the range, depth and reliability of mathematics. Following the implicit rules for forming and manipulating algebraic expressions makes it much easier to avoid making a mistake—but it’s still easy to divide by zero without noticing, unless you pay attention to the meaning of what you’re doing as well as the syntax. Mathematicians can gain clarity and rigour by exploiting the human capacity for visual and kinetic imagination, either by inward imagining or by using diagrams or physical models (this is Avigad’s eighth heuristic). They can exploit Peircean iconicity, because mathematics is about structure, so we can use representations that share structure with the objects under investigation.Footnote 17 Increasingly, as the variety of mathematical domains grows, mathematicians can create arguments by moving between different parts of mathematics. Ken Manders calls this the ‘conceptual agility’ of contemporary mathematics:

…hopping a functor to another category any time superfluous details are sensed (homology groups in topology); bringing in details seemingly extraneous to one’s question by a representing functor (group representations in the theory of abstract groups); explaining families of simple number-theoretic facts anyone can see one-by-one, by some hard to master ‘underlying’ abstract structure (Fermat’s problem).Footnote 18

Here Kevin Buzzard, a mathematician at the heart of the Lean proof formalisation project, makes a similar point:

Mathematicians [are] so good at instantly switching between the various ‘obviously equivalent’ ways that a mathematician looks at a complicated algebraic object (‘It’s an equivalence relation! Now it’s a partition! Now it’s an equivalence relation again! Let your mental model jump freely to the point of view which makes what I’m saying in this particular paragraph obvious!’, or ‘Matrices are obviously associative under multiplication because functions are associative under composition.’... Some of the proofs we’re writing [in Lean] are simply proofs that humans are behaving correctly when using mathematical objects. (Buzzard 2020)

Proving that the moves mathematicians make are correct is not the same activity as making those same moves more slowly in a less rich notation.

These jumps are helpful precisely because they allow us to bring domain-specific techniques from one area to bear on a problem first found in another. A detour through complex analysis in order to solve a problem in real analysis, or a visit to real analysis to help prove a result in number theory, does not look much like re-coding of syntactic data. It is more like moving from one natural language to another in search of the mot juste or looking for legal arguments in a different area of law from the case in hand. Mathematicians translate problems and proof-ideas between different parts of mathematics all the time, and translation of a proof into a foundational idiom is just a special case of this. Rather than choosing a metaphor to describe translation between informal proofs and formal derivations with the aim of preserving the Standard View, it might be less question-begging to work up a general account of intra-mathematical translation on a broad evidence-base, and then see what it says about the special case of translations of proofs into formal derivations.

This view of mathematics as a meaningful human reason-giving activity appears in places in Avigad’s article. He notes that mathematical proofs written for human use are robust in the sense that that they can survive errors of syntax and abuses of notation—in fact, abusing notation tactically is an important mathematical skill, but this thought makes no sense if proofs are syntactic items. They’re also insensitive to minor mistakes in calculations or localised reasoning, because readers can correct the errors (as Avigad observes). This can only be because readers understand what the inferences are about and are not simply processing symbol strings syntactically. Some of Avigad’s heuristics—analogy, generalisation, abstraction, exemplification, classification and visualisation—only make sense as strategies for handling meaningful mathematical content. An analogy is not, at the point where it is useful, a syntactic relation. Strategic generalisation is not something a machine can do, not least because very often more than one generalisation is available (for example, if you know something about equilateral triangles, you might generalise to other planar regular polygons or you might generalise to simplexes in higher dimensions). Similarly, noticing that there is a structure in common that is open to axiomatisation, identifying examples that will be both tractable and informative, and classifying in a way that carves the domain at the joints all depend on familiarity with and understanding of mathematical content. It’s true that these activities are preparations for proving rather than parts of proofs. However, it is implausible to suppose that the same mathematical content suddenly switches from being richly significant to become a series of syntactic operations when it is tidied up and arranged into a proof.Footnote 19 One of Avigad’s metaphors makes the very point:

Comparing proof to a narrative allows us to draw on intuitions regarding the distinction between the plot and its syntactic presentation. After reading Pride and Prejudice, we can reliably make the claims about the characters and their motives, but we cannot reliably make claims about the number of occurrences of the letter ‘p.’ If the judgment as to the correctness of a proof is more like the former, we have a chance; if it is more like the latter, it is hopeless. (2020, p. 8)

Evidently, Avigad favours the former option: thinking about the correctness of a proof is more like making judgments about the plot and characters of a novel, than it is like guessing how many times a letter occurs in the manuscript. This thought, however, undermines the metaphors in his paper that encourage syntactic readings of informal proofs. The relation between the plot of a novel and the typescript is not like data-compression or code-compiling. Turning a plot-and-character idea into a fully written out novel is not a routine translation, in any sense of ‘routine’, let alone in the sense that Hamami develops in his paper.

To fix ideas, consider this example: prove that given any two potatoes, there is a closed loop of the same size and shape on both skins. Like many mathematical proofs in philosophy articles, this is very short and untechnical. It is in these respects quite unlike typical proofs in research mathematics, but it is nevertheless a mathematical proof so whatever we say about mathematical proofs in general must be true of it. The solution is in thisFootnote 20 footnote. It is, of course, possible to translate this proof into the language of contemporary geometry and thence into a suitable foundational language, so that it no longer relies on spatial intuition and the inferences are all applications of inferential rules of the general logic of the chosen foundational idiom. The issue is the nature of this translation. According to Hamami, and to Avigad when he follows Hamami, the relation between the proof as offered here and its corresponding derivation is one of data-compression. For this to be true, the proof as written here must already be a syntactic object, and the reasoning in it must be the application of wholly general syntactic rules. It is, of course, possible to conceive of it thus, but in doing so, we would be re-reading it in order to save a philosophical theory from refutation. Alternatively, we could take it to be what it seems to be, namely, a piece of spatial reasoning that works not by manipulating meaningless symbol strings but rather by manipulating imagined potato surfaces.

This brings me to another difficulty Hamami’s computational picture of the translation between informal proof and formal derivation: it undersells the achievement of the foundational programmes in mathematics. Avigad sometimes wonders aloudFootnote 21 why critics of the Standard View seem to want to disregard the great advances in rigour achieved by twentieth-century mathematics. It is wonderful that it is now possible in principle to check any piece of mathematical reasoning mechanically, that mathematicians can pursue piecemeal formalisation as far as they need to in any given case, and that there is a growing library of fully formal proofs of significant theorems.Footnote 22 However, if we think of mathematics as carried out by humans as syntactic processing, as the data-compression and code-compilation metaphors require, then this becomes less of an achievement. If all mathematical thinking is and always was syntactic processing, then the great foundational programmes did nothing more than set up the compilation tables. The real wonder, the deeply significant achievement, is that it is now possible, with enough work, to check even the most richly human mathematics by machine. It is as if we could judge the coherence of the plot of a novel by asking a computer to count the ‘p’s in the manuscript. Hamami’s view of translation undervalues this achievement and misdescribes the work involved in preparing a proof for mechanical checking. In Avigad’s paper, there is already a hint about how the formalisation of meaningful human mathematics is possible: many of the heuristics described in the observational core of Avigad’s paper simultaneously support the rigour of the informal proof and prepare it for translation into a more formal idiom. Following this clue may help us to understand how machine proof assistants are useful to mathematicians, but only if we resist any temptation to begin by positing that human mathematicians were machines all along.

5 Conclusions

I have argued for two claims in this paper. The first is that the observational core of Avigad (2020) is independent of the Standard View that formalisability is the criterion of correctness for mathematical proofs. In doing so, I distinguished between ‘strong’ versions of the Standard View that claim that sound informal proofs are, in spite of appearances, really syntactic objects and that when mathematicians read them, they’re doing some sort of syntactic processing, and ‘weaker’ versions that don’t have that commitment. My second claim is that Avigad, in his (2020), havers between these two versions of the Standard View. He is not alone in this—the tension between these two options is present in the debate from Mac Lane onwards. For the discussion to advance, proponents of the Standard View need to specify which version they endorse.