The Zero Paradox: A Reader’s Guide
Plain-language introduction, illustrated companions, and reading paths for all audiences.
For a dictionary and map of ⊥ - the object the whole framework is built on - see The Bottom Element. For the formal framework, Lean verification, and complete question register, see the Formal Index.
Interactive - The Bottom Family tree. A single visual map of ⊥ across the fields: hover any node to see why it lands where it does, with the checkable Lean witness. The clearest one-picture view of what the framework assembles.
Followed a link that broke after the v3.0 source reorganization? Report anything stale in the v3.0 reorg link-integrity thread.
What This Is
The Zero Paradox proves that a minimum non-bottom element is structurally forced - not assumed - given the framework’s discrete state model (a bare join-semilattice alone can be dense, with no such minimum; that is exactly where the transition fails, in the reals). The result is machine-verified in Lean 4. The supporting structure examines what happens at the bottom element ⊥ across several mathematical frameworks; each independently locates the same structural constraint. One additional hypothesis per framework is required that is not derivable from that framework’s axioms alone - these are catalogued in Axiomatic Commitments in README.md.
Each layer of the proof is internally closed before any cross-framework claim is made.
No snap-specific axioms appear anywhere in the framework. The Binary Snap - the forced transition from the bottom element ⊥ to the minimum non-bottom state - is a theorem proved in ZP-E from A4 - the standard bottom-element axiom (∀ x, ⊥ ∨ x = x) - together with the framework’s computational commitments. A4 is a standard axiom of join-semilattice theory.
What This Is Not
- Not a physical theory - the framework is silent on which specific state emerges first; physical theories would arise by specifying that
- Not a claim about consciousness or the hard problem - the framework is silent on these questions
- Not a claim that zero is paradoxical in all of mathematics - the paradox is local to this framework’s structure
- Not a logical contradiction - the framework is internally consistent throughout
On vocabulary. The framework aims for precision by using the established term for each structure it describes - the recognized name from the relevant field, not a coinage of its own. (Its own results carry reference labels - T-SNAP, MC-1, and the like - as any formal development assigns; those are identifiers for specific results, not invented vocabulary for existing structures.) A deliberate consequence is that its language draws on concepts from many backgrounds: set theory, category theory, proof theory, computability, valuation theory, and others. Borrowing a field’s precise vocabulary is not a claim to results in that field; the framework’s assertions are confined to the mathematics it formally establishes, and where its structures resemble ideas in other domains, those resemblances are named as such, never asserted as results there.
Entry Point
Ask questions about the framework
This repository is connected to a Copilot Space - a GitHub AI chat with the documents and Lean source indexed. It has been given project-specific context, so it can help orient you to the layer structure and terminology.
Open Copilot Space - GitHub account required.
| File | Description |
|---|---|
| Zero Paradox Foreword | Plain-language introduction for any reader. Start here. |
Reading Paths
Before any path: The Bottom Element (⊥) - a dictionary and map of the object the whole framework is built on - and its companion The Binary Snap (⊥ → ε₀) - the same for the snap, the transition off ⊥. Together they orient you to ⊥ and the snap, and to what is proved versus still open about each, before you follow any route below.
General reader: The Philosophical Question → Foreword → any Illustrated Companion → ZP-E Companion → ZP-I Companion (framework closure)
Mathematician: the formal layers are best read by field, not in one linear sequence. See the Reading Order (by Specialty) in the formal index, which routes each specialty (number theory, proof theory, computability, set theory, category theory, order and analysis) through its own layers, the bridge that connects it, and the shared bottom ⊥.
Category theory extension: ZP-G → ZP-H → ZP-H Native Categories Addendum (self-contained after ZP-E)
For process and methods: ZP Tools and Methods
Illustrated Companion Documents
One companion per formal document. Plain language, diagrams, real-world examples.
Note (April 2026): Some companions were written before significant revisions to the formal documents and are currently being updated. Treat them as introductions to the framework’s structure, not authoritative statements of current theorem names or statuses.
| File | For Document | Key Diagrams |
|---|---|---|
| ZP-A Illustrated Companion | ZP-A | Hasse diagram, one-directional transitions |
| ZP-B Illustrated Companion | ZP-B | Nested clopen balls, disjoint ball separation |
| ZP-C Illustrated Companion | ZP-C | Surprisal field singularity, 1-bit Snap cost, L-RUN execution trace |
| ZP-D Illustrated Companion | ZP-D | T map: topology → orthogonality |
| ZP-E Illustrated Companion | ZP-E | Four-framework convergence, T-SNAP derivation chain |
| ZP-F Illustrated Companion | ZP-F | ℝ vs Q₂ structural comparison, pi curve density diagram |
| ZP-G Illustrated Companion | ZP-G | Category and functor concepts, initial object, informational singularity |
| ZP-H Illustrated Companion | ZP-H | Four-functor convergence, T-SNAP derivation chain, Binary Snap across the four ZP frameworks |
| ZP-I Illustrated Companion | ZP-I | 2-adic depth diagram, three closed doors + Cauchy passage, complete cycle diagram |
| ZP-J Illustrated Companion | ZP-J + ZP-J AFA Addendum | Quine atom diagram (⊥ = {⊥}), directed-graph (APG) view of the Quine atom (self-loop), three-way equivalence table, CC-1/CC-2 as derived propositions, abstraction chain (ValuationStructure → AFAStructure), APG decoration uniqueness |
| ZP-J Wheel Illustrated Companion | ZP-J Wheel Addendum | Wheel vs meadow diagram (∞ ≠ ⊥), division by zero made total, ∞ = /0 and ⊥ = 0·/0, the wheel of fractions construction, wheel/meadow distinction, porthole connection |
| ZP-K Illustrated Companion | ZP-K | Four-way equivalence diagram, computational Quine, execution argument Lean verification |
| ZP-L Illustrated Companion | ZP-L | Ordinal tower with ε₀ snap threshold, dual convergence diagram |
| ZP-M Illustrated Companion | ZP-M | Kleene-Ordinal-2-adic triangle, diagonalization schema |
Supporting Documents
| File | Description |
|---|---|
| The Philosophical Question That Started This | The philosophical question that motivated the framework, and what the formal results say about it. |
| ZP Tools and Methods | How the framework was developed: Claude’s role, what formal tools were and were not used (Rocq, Lean, etc.), the PDF rendering pipeline. |
| Forced but Not Proved: A Reader’s Guide | Plain-language guide to the framework’s confidence labels. What “proved,” “forced,” “chosen,” and “open” mean, and why some results are chosen rather than proved. The accessible companion to Forced Metatheoretic Commitment. |
Notes on Development
This framework was developed by a human researcher in collaboration with Claude (Anthropic, April 2026). Claude served as research assistant, formal scribe, and gap identifier. All mathematical content and theoretical direction originated with the researcher. See ZP Tools and Methods for a complete account.
The PDF build tooling is publicly available in the scripts/ folder. Those scripts were generated by Claude and are included for transparency about how the documents were produced.
If you find this work valuable and would like to support its continued development, you can do so via GitHub Sponsors.
Repository and Version History
This project is hosted on GitHub at timbrigham/ZeroParadox. The repository uses Git for version control, allowing you to explore the evolution of the theorems and documents over time.
To view older versions of documents as the framework progressed:
- Via GitHub web interface: Navigate to the repository, click on a file, then “History” to browse commits.
- Locally: Use
git logto see commit history andgit checkout <commit-hash>to view specific versions.
Previous document versions are preserved in the git history and browsable at each release’s Zenodo snapshot, keeping the full development history recoverable.
For the formal framework, axiomatic commitments, question register, and Lean verification, see the Formal Index.
| *Zero Paradox | April 2026* |