LEM0002canonicalv1Pentation Non-Injectivity
No fifth orbit channel exists (K6), so pentation cannot be equipped with canonical injectivity within tau.
Payload
Pentation Non-Injectivity
No fifth orbit channel exists (K6), so pentation cannot be equipped with canonical injectivity within tau.
Pentation Non-Injectivity
Summary
No fifth orbit channel exists (K6), so pentation cannot be equipped with canonical injectivity within tau.
Statement
%
\label{lem:pentation-non-inj}
There is no orbit channel available to host a level-4 operation.
Consequently, pentation cannot be equipped with
a canonical injectivity proof within $\tau$.
Proof / Justification
[Proof sketch]
A canonical injectivity proof for the level-$k$ operation
requires that the operation's ``type information''
be encoded in a dedicated orbit channel.
At levels 0--3, the four channels
$O_\alpha, O_\pi, O_\gamma, O_\eta$
provide this encoding.
At level~4, a fifth channel would be needed.
But by $\KAxiom{6}$ (Object Closure),
$\Obj(\tau) = \{\omega\} \cup O_\alpha \cup O_\pi
\cup O_\gamma \cup O_\eta$.
There is no fifth orbit ray.
The beacon $\omega$ is a singleton and cannot host
a countably infinite type channel.
Therefore, pentation lacks the structural scaffold
for canonical injectivity.
Without canonical injectivity,
the operation cannot serve as a coordinate function
in the normal form decomposition (Part~V),
and the ladder terminates.
Source Context
- Registry source:
book-01.jsonlline 44 - Manuscript source:
2nd-edition/book-i-categorical-foundations/02_mainmatter/part02/ch08-iterator-ladder.texlines 206-212
Lean / Formalization Notes
- Formalization:
formalized - Module:
TauLib.BookI.Orbit.Ladder - Name:
Tau.Orbit.pentation_non_inj
Dependencies
- Canonical: I.D06, I.K6, I.D03
Related Results
Generated by later projection phases.
Related Publications
Generated by later projection phases.
Revision Notes
- 2026-04-24: Initial pilot migration.
Identifiers
Aliases & legacy IDs
I.L01pentation-non-injectivitylem:pentation-non-injRelease lines
corpus_v3_workingcorpus_v2Relations
Formalized by (1)
Appears in (1)
Downstream uses (computed) (2)
Items in the corpus that reference this one via load-bearing relations. Computed from the full corpus-v3 graph at build time.
Sources
Version & History
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.