Corpus definition canonical 2026-05-27T20:53:50+00:00
Corpus v3 · Definition cid001518DEF0288canonicalv1

Proof Theory as E₃

Proof theory is E₃ self-modelling applied to E₂ code. Layer Template at E₃: Carrier = formal systems as objects, Predicate = provability about provability, Decoder = metatheoretic interpretation, Invariant = metatheoretic consistency.

Payload

Proof Theory as E₃

Proof theory is E₃ self-modelling applied to E₂ code. Layer Template at E₃: Carrier = formal systems as objects, Predicate = provability about provability, Decoder = metatheoretic interpretation, Invariant = metatheoretic consistency.

Proof Theory as E₃

Summary

Proof theory is E₃ self-modelling applied to E₂ code. Layer Template at E₃: Carrier = formal systems as objects, Predicate = provability about provability, Decoder = metatheoretic interpretation, Invariant = metatheoretic consistency.

Statement

%
\label{def:proof-theory-as-e3}
\textbf{Proof theory} is the $\Elayer{3}$ self-modelling applied to $\Elayer{2}$ code.
Its four template components are:
\begin{enumerate}
    \item[\emph{(Carrier.)}]
    Formal systems as objects.
    The carrier is the class of $\Elayer{2}$ virtual machines---ZFC-VM
    (Definition~\ref{def:zfc-as-e2-vm}), Peano Arithmetic, type theories---each viewed
    not as a tool to be used but as a mathematical object to be studied.

    \item[\emph{(Predicate.)}]
    Provability about provability.
    Metatheoretic reasoning about a formal system must not contradict the system's own
    derivation behaviour: the metatheory is sound with respect to the object theory.

    \item[\emph{(Decoder.)}]
    Interpretation of metatheoretic results.
    The $\Elayer{3}$ decoder translates a syntactic metatheorem
    (e.g., ``ZFC does not prove $\mathrm{Con}(\mathrm{ZFC})$'')
    into a structural diagnosis (e.g., ``consistency is a host-level property'').

    \item[\emph{(Invariant.)}]
    Metatheoretic consistency.
    The host-level property of Chapter~\ref{ch:goedel-and-the-vm-boundary}
    is now the \emph{object of study}.
    At $\Elayer{2}$, consistency was the invariant---the property that the VM never crashes.
    At $\Elayer{3}$, proof theory investigates this invariant:
    which systems prove their own consistency?  Which do not?
    The $\Elayer{3}$ invariant is the stability of these conclusions
    under changes of metatheory.
\end{enumerate}

Proof / Justification

This item is definitional. No manuscript proof is required.

Source Context

  • Registry source: book-03.jsonl line 184
  • Manuscript source: 2nd-edition/book-iii-categorical-spectrum/02_mainmatter/part10/ch70-proof-theory-as-e3.tex lines 96-129

Lean / Formalization Notes

  • Formalization: formalized
  • Module: TauLib.BookIII.Mirror.ProofTheoryE3
  • Name: proof_theory_e3_check

Dependencies

  • Canonical: III.D05, III.D09, III.D67

Generated by later projection phases.

Generated by later projection phases.

Revision Notes

  • 2026-04-24: Initial pilot migration.

Identifiers

  • Corpus ID cid001518
  • Primary alias DEF0288
  • Type Definition
  • Status canonical
  • Visibility public
  • Version v1

Aliases & legacy IDs

III.D73proof-theory-as-edef:proof-theory-as-e3

Release lines

corpus_v3_workingcorpus_v2

Relations

Formalized by (2)

Appears in (1)

Downstream uses (computed) (4)

Items in the corpus that reference this one via load-bearing relations. Computed from the full corpus-v3 graph at build time.

Sources

  • Monograph cid000024Book III, Part 10, Chapter 70 (Part X)

Version & History

  • v1 · 2026-05-10 imported from v2 registry
  • v1 · 2026-05-10 wired formalized by in wave 5

Status disclaimer

A Corpus Item page reports the program's current internal record for this item. It does not imply external verification, scientific consensus, or final proof unless explicitly stated. Read it together with its dependencies, formalization status, and the program's overall stance.

Save or share this page for inspection

Download a portable dossier, copy a reviewer note, or send this page to someone who can inspect it.

Email to expert