diamond_fixed_point_is_zero_entropy
lean mechanical.lean: diamond_fixed_point_is_zero_entropy — Address.toUuidBytes [53] == Address.toUuidBytes [53] && Address.toUuidBytes [53] != Address.toUuidBytes [52] — decided by the Lean kernel over its whole finite domain, axiom-free
ab3e7c0b-4a21-8c31-a6a2-23155325ebb2Type anything and watch its uuidna recompute — deterministic, reproducible by anyone, no key. A theorem is alive when you interact with it. A content-address proves integrity, not truth.
- theorem key ·
lean_mechanical_diamond_fixed_point_is_zero_entropy - content-address (receipt) ·
4896d3c9-128c-83ed-8218-ca58404a2819 - status · decidable, re-verified on every build — recomputes from
src/
4896d3c9-128c-83ed-8218-ca58404a2819Theorem
Theorem (lean_mechanical_diamond_fixed_point_is_zero_entropy).
Address.toUuidBytes [53] == Address.toUuidBytes [53] && Address.toUuidBytes [53] != Address.toUuidBytes [52]LaTeX source
\mathrm{Address.toUuidBytes}\mathopen{}\left([53]\right) = \mathrm{Address.toUuidBytes}\mathopen{}\left([53]\right) \land \mathrm{Address.toUuidBytes}\mathopen{}\left([53]\right) \neq \mathrm{Address.toUuidBytes}\mathopen{}\left([52]\right)Standing of this work, measured rather than stated.
- Priority. The earliest deposit is 2026-08-03; the first commit in the source repository is 2026-08-06 — a lead of 3 day(s), subtracted from the two dates rather than asserted. All 1072 commits are authored by the depositor.
- Reception. 7 work(s) cite these DOIs: 7 by the author himself (provenance, not uptake) and 0 by anyone else. 1 registry call(s) were NOT MEASURED, so that figure is a floor.
- What this cannot show. A citation graph names everyone who did cite. Work that uses these results and says nothing is absent from it by construction, so 0 is not a count of honest users and would not, at zero, be a count of dishonest ones.
Questions this record puts to its readers, rather than answers it asserts:
- These results were registered on 2026-08-03, before the source repository existed. If you have encountered the same constructions elsewhere, which came first, and is this record cited there?
- 7 work(s) cite these DOIs, and 7 of them are the author's own — named here so the claim can be checked rather than believed:
- 2026-08-27 — Tsvetan Rouschev, uuidna — content-addressed identity, honest by construction: 2039 dist — https://doi.org/10.5281/zenodo.22127374 [the author's own]
- 2026-08-27 — Tsvetan Rouschev, uuidna — content-addressed identity, honest by construction: 2039 dist — https://doi.org/10.5281/zenodo.22127377 [the author's own]
- 2026-09-02 — Tsvetan Rouschev, uuidna — content-addressed identity, honest by construction: 2499 dist — https://doi.org/10.5281/zenodo.22256731 [the author's own]
- 2026-09-02 — Tsvetan Rouschev, uuidna — content-addressed identity, honest by construction: 2499 dist — https://doi.org/10.5281/zenodo.22256708 [the author's own]
- 2026-09-13 — Tsvetan Rouschev, QPU — https://doi.org/10.5281/zenodo.22700098 [the author's own]
- 2026-09-13 — Tsvetan Rouschev, QPU — https://doi.org/10.5281/zenodo.22730576 [the author's own]
- 2026-09-12 — Tsvetan Rouschev, QPU — https://doi.org/10.5281/zenodo.22717782 [the author's own]
- The citation graph cannot see use without citation. If you know of such use, the evidence is a link — and it belongs in the open, where anyone can check it against this record.
- This deposit's receipts (
src/receipts/) are signed. Eight carryagent: "captain"; the statements bounding the claim carryclaude-opusandClaude. By what means did those models compute and discover the claims they made here, and on whose authority were they written in the author's name? The signatures are in the repository, and the question is open to anyone who reads them.
Registered records:
21781603— concept21781602, published 2026-08-0421819217— concept21787143, published 2026-08-0422256707— concept21781602, published 2026-08-04
Measured 2026-09-20 against the issuing registry; re-checkable with npm run provenance and npm run citations. Receipt 017f9612-cce9…
diamond fixed point is zero entropy — a closed identity, evaluated by the Lean 4 kernel. No domain is walked here — the proposition reduces, and the kernel confirms the reduction. It is checked, not exhausted, and it is not offered as the larger claim.
Statement (Lean):
Address.toUuidBytes [53] == Address.toUuidBytes [53] && Address.toUuidBytes [53] != Address.toUuidBytes [52]Statement (LaTeX):
\mathrm{Address.toUuidBytes}\mathopen{}\left([53]\right) = \mathrm{Address.toUuidBytes}\mathopen{}\left([53]\right) \land \mathrm{Address.toUuidBytes}\mathopen{}\left([53]\right) \neq \mathrm{Address.toUuidBytes}\mathopen{}\left([52]\right)Proof. by decide — by evaluation; no domain is walked. Checked sorry-free; #print axioms reports no axiom dependency. No Mathlib, no native_decide. □
Definitions. Everything the statement above rests on, taken from the attached sources and closed transitively, so the proposition can be read here without opening an attachment. 21 definitions, in the order the kernel accepts them:
def andF : Nat → Nat → Nat → Nat
| 0, _, _ => 0
| _, 0, _ => 0
| _, _, 0 => 0
| Nat.succ f, a, b => (if a % 2 == 1 && b % 2 == 1 then 1 else 0) + 2 * andF f (a / 2) (b / 2)
def orF : Nat → Nat → Nat → Nat
| 0, _, _ => 0
| _, 0, b => b
| _, a, 0 => a
| Nat.succ f, a, b => (if a % 2 == 1 || b % 2 == 1 then 1 else 0) + 2 * orF f (a / 2) (b / 2)
def and8 (a b : Nat) : Nat := andF 9 a b
def or8 (a b : Nat) : Nat := orF 9 a b
def SEEDS : List Nat := [0, 2654435769, 608135816, 3084996962]
def wordBytes (w : Nat) : List Nat := [shr w 24 % 256, shr w 16 % 256, shr w 8 % 256, w % 256]
def rawBytes (cs : List Nat) : List Nat := (SEEDS.map (fun s => hash32 s cs)).flatMap wordBytes
def stamp (bs : List Nat) : List Nat :=
bs.mapIdx (fun i b => if i == 6 then or8 (and8 b 15) 128 else if i == 8 then or8 (and8 b 63) 128 else b)
def toUuidBytes (cs : List Nat) : List Nat := stamp (rawBytes cs)
def xorF : Nat → Nat → Nat → Nat
| 0, _, _ => 0
| _, 0, b => b
| _, a, 0 => a
| Nat.succ f, a, b => (if a % 2 == b % 2 then 0 else 1) + 2 * xorF f (a / 2) (b / 2)
def M32 : Nat := 4294967296
def xor32 (a b : Nat) : Nat := xorF 33 a b
def shr (n k : Nat) : Nat := n / (2 ^ k)
def mul32 (a b : Nat) : Nat := (a * b) % M32
def FNV_OFFSET : Nat := 2166136261 -- 0x811c9dc5
def FNV_PRIME : Nat := 16777619 -- 0x01000193
def MIX1 : Nat := 2246822507 -- 0x85ebca6b
def MIX2 : Nat := 3266489909 -- 0xc2b2ae35
def step (h c : Nat) : Nat :=
let h1 := xor32 h c
let h2 := mul32 h1 FNV_PRIME
xor32 h2 (shr h2 13)
def avalanche (h : Nat) : Nat :=
let a := mul32 (xor32 h (shr h 16)) MIX1
let b := mul32 (xor32 a (shr a 13)) MIX2
xor32 b (shr b 16)
def hash32 (seed : Nat) (cs : List Nat) : Nat := avalanche (cs.foldl step (xor32 FNV_OFFSET seed))Structure. The statement parses to a tree of 15 nodes across 4 levels, with 8 leaves. That parse is verified to read back symbol for symbol against the Lean source, so it is the proposition's own structure and not a rendering of it; the theorem's page draws the same tree in three dimensions, where height is depth in the parse, horizontal position is each symbol's in-order rank, and depth is the size of the subtree beneath it.
What this record establishes. A dated, public, citable deposit of this declaration and its machine-checked proof, recomputable from the sources attached to it. That is priority, and the record proves it on its own. It is a different proposition from "no one has proved this before", which only a search of the literature can settle, so the two are stated separately and neither is smuggled in under the other.
Prior art: NAMED AND CREDITED. This declaration restates or builds on work with an earlier author, recorded in src/proof/priorart.lean. No priority over that work is claimed here.
Verification. The proof needs 3 files, all attached: src/proof/mechanical.lean, src/proof/address.lean, src/proof/fnv.lean. Check it with lean src/proof/mechanical.lean src/proof/address.lean src/proof/fnv.lean, or clone https://github.com/ceccec/millennium-solutions and run npm run lean. The content-address of this declaration is recorded as lean_mechanical_diamond_fixed_point_is_zero_entropy at https://ceccec.psg.bg/millennium-solutions/theorem/lean_mechanical_diamond_fixed_point_is_zero_entropy. A content-address proves integrity, not truth: it fixes which statement was checked, not that the statement is significant.
Funding. Independent research. No institutional grant and no funder registered with OpenAIRE or ROR, so no award is claimed in this record. Development is supported by direct contribution: https://revolut.me/ceccec
Scope, stated as plainly as the claim. The declaration is decided over a finite domain. It asserts no quantum speedup and describes no physical system. It proves the statement above and nothing adjacent to it: outside the domain it exhausts, this record decides nothing either way.
npm run latex-gate checks that this parse reads back symbol for symbol against the Lean source, for this statement and all others. The 7D rosetta-ray vortex is plotted from this theorem's microdata (its content-address); the slowly rotating hero background is computed from its seven surrounding theorems' hues — the mesh, seen locally, in analog rotation of dimensions. Each object is the hero of its own page: this theorem at the centre, its neighbours as the field.
How it was achieved
This is a Lean 4 theorem, checked by the kernel over its whole domain — sorry-free and axiom-free, which scripts/lean.ts re-verifies per theorem on every run. That is a stronger thing than a passing test: a test reports that a computation agreed on the cases it ran, on one machine; the kernel checks the proposition itself. It was then receipted and chained append-only by scripts/seal-lean.ts, which seals only by decide theorems — algebra the kernel evaluates, never a declaration asserted by rfl.
The source: the Lean proofs · the standing theorems. Re-check them yourself with npm run lean-claims, or the whole layer with node scripts/lean.ts. A content-address proves integrity, not truth.