Addressability
4 modules.
Book and family structure of the Corpus-owned TauLib projection.
TauLib follows the Corpus construction rather than standing outside it. Module families track books, construction layers, and local formalization neighborhoods.
4 modules.
39 modules.
1 module.
13 modules.
9 modules.
12 modules.
4 modules.
4 modules.
3 modules.
7 modules.
8 modules.
21 modules.
8 modules.
13 modules.
1 module.
7 modules.
7 modules.
3 modules.
6 modules.
5 modules.
9 modules.
5 modules.
5 modules.
1 module.
5 modules.
6 modules.
6 modules.
1 module.
9 modules.
8 modules.
6 modules.
10 modules.
3 modules.
2 modules.
3 modules.
7 modules.
1 module.
4 modules.
13 modules.
4 modules.
1 module.
6 modules.
15 modules.
3 modules.
17 modules.
6 modules.
3 modules.
7 modules.
11 modules.
7 modules.
6 modules.
8 modules.
1 module.
12 modules.
5 modules.
18 modules.
7 modules.
5 modules.
13 modules.
5 modules.
2 modules.
7 modules.
6 modules.
1 module.
2 modules.
2 modules.
7 modules.
4 modules.
4 modules.
2 modules.
2 modules.
4 modules.
3 modules.
1 module.
1 module.
1 module.
1 module.
4 modules.
1 module.
1 module.
1 module.
8 modules.
7 modules.
1 module.
Architecture here means Corpus architecture: modules, imports, and Registry anchors. Verify uses this architecture to ask higher-level questions about coverage, bridge adequacy, and claim boundaries.
TauLib does not import Mathlib.CategoryTheory or instantiate the Mathlib Category typeclass on TauObj. The categorical structure of τ is realized through hand-rolled morphism types (CatTau, HolEndCat, TauArrow, id_arrow, arrow_comp_stage) defined within TauLib itself, rather than as an instance : Category TauObj.
This is a deliberate architectural choice — the program treats τ as a categorical structure in its own right, with the morphism layer earned from K0–K6 and the progression operator ρ rather than inherited from Mathlib’s general category-theory hierarchy. A reviewer should expect to find:
class Category / def Hom / Iso constructions inside TauLib/BookI/Category/… and TauLib/BookII/Categorical/…, not via Mathlib instances.CategoryTheory is used as a comparison target) is on the formalization roadmap; it is not part of the current release.The K0–K6 themselves are realized in TauLib as theorems-by-construction over the inductive Generator and TauObj types — i.e. they hold for the chosen representation by definition of how those inductives are built — rather than as Lean axiom declarations in the strict TCB sense. The three custom axioms that do sit outside Mathlib’s trusted base are inventoried separately at Custom Axioms; K0–K6 are not among them. This is why the program describes K0–K6 as the kernel’s structural commitments on the marketing surface rather than as its TCB axioms.
Download a portable dossier, copy a reviewer note, or send this page to someone who can inspect it.