Skip to main content

A registered result in its source context

Original ledger classification: Exact [E] anchor identity + honest [E] generic/specific split + honest negative (no code reading of the p-sequence) + selective kill control (Python-only per GATE.WOLFRAM.02).

Recorded statement: The RM(1,3) reverse reading -- are compiler numbers CODE operations? (one module, 20 checks, ~1 s; discovery probe rm13_reverse_probe.py 20/20; exact integer arithmetic). An honestly TWO-PART answer. THE ANCHOR IDENTITY [E, central]: the…

Statement, assumptions and sources

Paper context: input 5 tfpt 3 e8 audit bootstrap

The exact identifier, original classification and full claim are available below.

The source wording and classification below are preserved as recorded. A paper link, shared script or authored topic relation does not upgrade the claim or report a new proof run. Read later reviewed findings separately.

Read the exact registered claim and its dependencies

E8.RM13REV.01

Original ledger classification: Exact [E] anchor identity + honest [E] generic/specific split + honest negative (no code reading of the p-sequence) + selective kill control (Python-only per GATE.WOLFRAM.02).

Original claim text

The RM(1,3) reverse reading -- are compiler numbers CODE operations? (one module, 20 checks, ~1 s; discovery probe rm13_reverse_probe.py 20/20; exact integer arithmetic). An honestly TWO-PART answer. THE ANCHOR IDENTITY [E, central]: the sigma-fixed syndromes of the equivariant placement C* are EXACTLY {0, s(e6), s(e7), q} with coset-leader weights (0, 1, 1, 2) and norm-square sum 6 = (1,1,2).(1,1,2); the anchor is the family sum in the quotient (P3 = P0+P1+P2); ALL four pair sectors carry (1,1,2)/norm 6 but ONLY the anchor pair is sigma-stable (pointwise fixed) -- the sigma action SELECTS the anchor copy. HONEST SPLIT [E]: the (1,1,2)/norm-6 weights per pair sector are GENERIC for any [8,4,4] placement (R3.2: the naive placement carries them too); equivariance-specific are ONLY q-universality, the sigma-fixing of the anchor sector, and anchor = family sum (R3.1: all die for the naive placement). THE BYTECODE NEGATIVE [E, honest]: the 42-entry invariant battery lands the structural anchors exactly (240 = #roots, 8 = n, 248 = roots + n, 60 = roots/4, 12 = #sigma-fixed roots, 6 = anchor norm = #pair-unions) -- but the p-sequence (4, 6, 10, 18) of p_n = 2 + 2^n has NO code reading (0/11 natural families), 27 and 81 have no hit at all, 18 no hit, 10 only as a C*-specific Z6-orbit count: the bingo is buried. KILL CONTROL [E]: fires selectively -- the orbit censuses (6, 10) and the sigma/anchor selection die for non-equivariant placements, the pure-code invariants and even the sigma-fixed-root COUNT 12 do not (R3.6 honest correction: naive also has 12; only the mod-2 fibration is C*-structure). No marker moves.

Original classification detail

RM13-REVERSE-TWO-PART: the anchor decomposition (0,1,1,2)/norm 6 is exact with the sigma action selecting the anchor sector (selection equivariance-specific, weights generic); the bytecode p-sequence has NO code reading (0/11 families, 18/27/81 no hit) -- honest negative, route closed; kill control selective; no marker moves.

Dependencies as recorded

E8.CODESEM.01; E8.CODE.01; EXTREV.LATTICE.01; v624; v626; v638

Open the original ledger source, row 650

Location recorded in the ledger

These document locations are recorded directly on the ledger row. They are document level navigation, rather than a newly inferred section citation.

Sections that explicitly cite this claim

A literal claim identifier is present in these paper sections. The section and its premises determine what the citation supports.

Navigation through a shared verification script

These sections cite a script associated with the claim. This is a source navigation join, rather than an explicit citation of the claim or a theorem equivalence.

Registered verification modules

  • v646_rm13_reverse.pyRegistered verification module · core
    Read the description recorded in the module registry

    E8.RM13REV.01: die RM(1,3)-Rückwärts-Lesung — sind Compiler-Zahlen CODE-Operationen? **EHRLICH ZWEIGETEILT: die σ-fixierten Syndrome tragen EXAKT die Anker-Zerlegung (Leader-Gewichte (0,1,1,2), Norm 6, Anker = Familiensumme P3 = P0+P1+P2 — die AUSWAHL ist äquivarianz-spezifisch, die Gewichte selbst generisch für jede [8,4,4]-Platzierung), aber die Bytecode-Folge p_n = 2+2ⁿ hat KEINE Code-Lesart (0/11 Familien; 18/27/81 ohne Treffer — das Bingo ist beerdigt)**; Kill-Kontrolle feuert SELEKTIV (naive Platzierung verliert q-Universalität + σ-Aktion, behält generische Gewichte und sogar den Zähler 12 — ehrlich umgetypt) (20 checks, ~1 s)

A registered module is a source reference. Its presence does not assert that the module was executed in this snapshot.