Corpus Lane Root Canonical The construction body of the theory: definitions, derivations, monographs, registry objects, TauLib projection, and dependency relations.
Lane RootCanonical

Corpus

The construction body of the theory: definitions, derivations, monographs, registry objects, TauLib projection, and dependency relations.

Research body
Definitions, lemmas, theorems, structures, and dependency relations.
Construction spine
The public build-order narrative traces the Corpus through ten canonical construction steps.
Public projections
The Corpus appears through Construction Spine, Monograph Corpus, Registry, TauLib, Corpus Graph, Results, Verify, and Publications as distinct public surfaces.

What the corpus is

The Corpus is the construction body of the theory.

The Construction Spine gives the ten-step public build order.

The Monograph Corpus shows how the seven-book monograph series realizes that build order across books, parts, and chapters.

The Registry exposes atomic objects. TauLib exposes formal proof surfaces where available. The Corpus Graph exposes dependencies. Results shows what follows. Verify shows how the build can be inspected. Publications holds citable release artifacts.

For the implementation view of how Corpus, Results, Verify, Publications, and Engage are connected as public surfaces, see Building a Public Research Observatory for High-Scope Open Research.

The build-order at a glance

The Construction Spine

Scientific plate titled The Construction Spine, showing a vertical ten-step build sequence from Kernel to Ontic Closure, with side projections for Registry, TauLib, Monograph Corpus, and Corpus Graph.
The Construction Spine is the Corpus-side build narrative: ten canonical steps from kernel definition through mathematics, physics, life, reflective structure, self-hosting, and ontic closure, with public projections through the Registry, TauLib, Monograph Corpus, and Corpus Graph.

↓ Download print master · 1536 × 864 JPG · CC BY 4.0

The Construction Spine is the primary human-readable route into the Corpus. It shows the build-order narrative from kernel definition through mathematics, physics, life, reflective structure, self-hosting, and ontic closure. The spine’s End-to-end construction view shows how the ten steps form a single construction chain, with each step inheriting what earlier steps have earned and handing forward what later steps need.

Corpus Artifact Projections

The Corpus is updated by — and connected to — the active publication stream. Publications-class artifacts that touch the Corpus appear in five projections:

The τ-Kernel

Scientific plate titled The τ-Kernel, showing five generators, one primitive iterator, a central τ-Kernel block, K0–K6 axiomatic constraints, constructive closure, and boundary notes for no hidden runtime and no hidden substrate.
The τ-Kernel is the constrained formal core from which the construction begins: five generators, one primitive iterator, K0–K6 axiomatic constraints, and constructive closure under a no-hidden-runtime / no-hidden-substrate discipline.

↓ Download print master · 1536 × 864 JPG · CC BY 4.0

The τ-Kernel is the formal starting point of the construction. It is not a hidden physical substrate; it is the constrained formal core from which the Corpus begins.

The Bi-Square Motif

Scientific plate titled The Bi-Square Spine, showing a two-by-three pasted diagram with tower coherence on the left, spectral naturality on the right, and a pasting constraint across the whole rectangle, followed by a scaling chain from algebraic to geometric, enriched, and computational bi-squares.
The Bi-Square Motif shows the repeated categorical shape that carries the kernel through its main lifts: tower coherence on the left, spectral naturality on the right, and a pasted constraint that becomes richer at each layer.

↓ Download print master · 1536 × 864 JPG · CC BY 4.0

The Bi-Square Motif is the Corpus route for the repeated proof-organizing diagram behind the kernel buildup. The Construction Spine gives the build order; the bi-square gives a stable categorical shape that reappears as algebraic, geometric, enriched, and computational structure. It is a construction motif, not a second construction spine.

Construction Steps 1-3 review packet

The first three construction steps have a dedicated reviewer packet route: eight foundational research papers plus a bundle memo, surfaced through Corpus-native gateway pages. These pages explain how the kernel is built, how core mathematics is recovered, and how self-enrichment begins. They are an orientation and stress-test packet, not a standalone Corpus collection.

Corpus projections

The same construction body appears through several public projections:

Orientation routes

These routes are preserved because they are useful for review, but Wave 3 treats them as construction metadata rather than top-level Corpus peers.

Current state

The current registry is the public atomic projection of the corpus. The primary human-readable route into the Corpus is the Construction Spine: the build-order narrative from kernel definition through mathematics, physics, life, reflective structure, self-hosting, and ontic closure.

What the Corpus is not

  • not a claim list; see Results;
  • not the citable artifact shelf; see Publications;
  • not the proof assistant itself; see TauLib and Verify;
  • not a frozen release; citable snapshots and release artifacts live in Publications;
  • not a replacement for verification; see Verify.

Structure

The Corpus lane is the place to ask: what has actually been built, how does one item depend on another, and where does a public result touch the underlying research body?

Frequently asked

A focused subset of FAQ entries on what the Corpus actually is, how to cite it, what’s in the Registry vs TauLib, and why count drift matters.

What is the Corpus?

The Corpus is the construction body of the theory: definitions, derivations, monograph exposition, registry objects, TauLib projections, and dependency relations.

The Corpus is where the theory is built rather than merely announced. It is not identical to the books, the Registry, or TauLib; those are projections of the Corpus. A reviewer asks there what was constructed, in what order, from what earlier obligations, and with which dependency anchors.

What is the difference between the Registry and TauLib?

The Registry is the object/dependency map of the Corpus; TauLib is the Lean formalization projection of selected formal content.

A registry object is a stable public ID for a Corpus item. A TauLib module is a Lean source file. The meaningful audit question is whether claimed mappings between Registry, Corpus, and TauLib are explicit and inspectable.

Why do counts sometimes differ between Registry, dashboards, and TauLib?

They count different units with different filter rules: registry objects, dashboard-display objects, formalized dashboard objects, Lean modules, and direct `sorry` counts.

Registry objects are not Lean modules. Dashboard totals are filtered views. Formalized counts apply status filters. `sorry` count is a source scan. The first question is always which filter rule each page uses.

How do I cite a specific result, paper, or registry object?

Cite books and papers through DOI/citation pages, cite results by stable URL and status label, and cite registry objects by stable object ID and permalink.

Use the publication artifact for citable works, stable Result URLs for claims, Registry IDs for atomic objects, and the Release Manifest/TauLib for formalization claims.

All 73 FAQ entries →

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