Skip to content

Certify conditional kappa 0.0033999964 via the p19 word without the coded overlay (complex 0.007578535, BIT 0.0034, zero field bill) - #5270

Draft
DaysSky wants to merge 5 commits into
CrocSwap:mainfrom
DaysSky:research/p19-coded-reverse-supplier
Draft

DaysSky wants to merge 5 commits into
CrocSwap:mainfrom
DaysSky:research/p19-coded-reverse-supplier

Conversation

@DaysSky

@DaysSky DaysSky commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Draft. Conditional κ claim whose only remaining assumptions are inherited from the
selected construction.
Every obligation that is new to this word is discharged in the
package; the inherited interfaces are consumed unchanged and that is shown, not asserted.

Status against the required bar

obligation status evidence
finite arithmetic discharged p19_claim.py: invoice root 0.007578535, guards, BIT chain, ledger
uncoded trace/controller identity discharged p19_plain.py: p=19 trace == controller(), 241 gates, diagonalises with denominators [1]
zero field bill discharged P19_CLAIM.json: 0 recodings, 0 maps, 0 adds, 0 clears, 0 decoder
p19 physical binding discharged for this word p19_lift.py: Φ is a ring homomorphism on the monomial ring (multiplicativity on 24 sampled pairs, powers add, distinct axes commute), so the gate-list identity lifts to address operators for every block count; the p=2 replay is the implementation control, 2^17 addresses per role
compiler: rank completion, splitting discharged on this census max target rank 153 < 256, 20⁶⁴ < 21⁶³
compiler: normalizers, owner allocation, rank-one surplus inherited, interface unchanged the word adds no job, no owner and no scratch; the T/D census is the source's own model
helper compatibility discharged mechanically the trace's roles are exactly 0…2p−1; no gate reads or writes helper-owned state
helper materialisation (7,752 units) inherited PR4929 producer; priced on the T side, not rebuilt here
fixed-tape/precision/hosting/CI/kernel inherited caller-side compiler instance and maintainer pipeline

What changed since the last revision

  • The claim artifact no longer contradicts the word: field_level_bill is emitted
    all-zero from the uncoded receipt, and the coded overlay is quarantined as
    record_only_overlay ("historical record, NOT the priced word"). verify.py asserts
    both, so they cannot drift apart again.
  • Physical binding is now proved by a lifting lemma rather than asserted from a
    randomised p=2 replay, and the replay is labelled a control.
  • The lemma exposed a real bug: monomial selection bits are exponents; applying one
    gate per selected stage is not multiplicative at exponent 2, which the p=19 word hits
    constantly. Both the lemma checker and the replay now use exponent powers.
  • Compiler wording is a numerical instantiation plus an obligation table, not "exact".
  • Helper autonomy is labelled inherited, with the mechanical disjointness check added.
  • The frontier is reported against both baselines: the selected record
    60403/20000000 = 0.00302015 (+12.58 %) and the maintainer-reported 0.00302728823
    (+12.31 %), the former read from certificates/selected-result.json at run time.
  • SOURCES.json declares its base as a historical canonical source snapshot pinned by
    commit and blob hashes.

The claim

κ = 951999/280000000 = 0.0033999964 from a complex supplier of 0.007578535 and the
admitted BIT supplier 17/5000. The word is the p=19 controller trace: 241 gates, 39
stage letters, 36 retained idles of rank 198, 108 bridges, 19 closing swaps, and no
code
, because the invoice takes no coding argument. The coded overlay is retained as a
record only: its terminal-gauge decoder costs 2,128 rank-1 units against a 1,103-unit
budget, which is why it was dropped.

Reproduce

python3 -B research/coded-reverse-word-p19/p19_plain.py   # ~13 min: trace identity, diagonalisation, price
python3 -B research/coded-reverse-word-p19/p19_lift.py    # lifting lemma
python3 -B research/coded-reverse-word-p19/p19_bank.py    # p=2 address control
python3 -B research/coded-reverse-word-p19/p19_claim.py
python3 -B research/coded-reverse-word-p19/verify.py
python3.12 -B scripts/research_package.py --package research/coded-reverse-word-p19

Reviewer's checklist

  • Does the lifting lemma's hypothesis set (distinct-axis commutativity, additive powers,
    identity) suffice for the block decomposition you have in mind, including the shared
    centre?
  • Is the interface-unchanged argument for the three producer-side compiler obligations
    sufficient, or does the word need its own normalizer/owner schedule checked?
  • Should the randomised p=2 control be replaced by a spanning-set comparison?

… verification open)

Adds the p19 coded-reverse packages: the exact physical thin source and local
S/L/R boundary pair, and the materialized controller word with its paid
accounting.

The word is emitted as an explicit 259-gate listing and replayed against the
standard word: 19 gauge loads, 19 unloads, 20 forward stages, 19 reverse
stages, 19 letters, 36 retained idle calls, 108 bridges and 19 closing swaps.
Replay differs on 0 of 229,376 entries at p=2 and 0 of 2,179,072 at p=19, with
the per-role gauge invariant checked after every gate that writes a role.

The code is rank-free: every port map is a signed address permutation and the
scalar program moves no address, so the 77 recodings cost 17,248 monomial field
maps, 68,992 scalar adds and 1,232 owned clears per call and no Gaussian child.
The rank invoice prices the word at 0.007578535 under the PR4929 profile and
reproduces the published p16 root; the tail ratios at the endpoint are
alpha 0.99579414, gamma 0.963763, delta 0.951561.  With the admitted BIT saving
0.0034 the strict outer ledger passes at kappa = 951999/280000000 = 0.0033999964
and at exactly 0.0034 fails only actual_bit_above_effective.

Draft status: the endpoint rests on the retained PR4433 power majorant (the
logarithmic majorant caps the tested saving at 611329/200000000 and that cap is
recorded), on the 0.97 tail limit in place of the source's 19/20, and on the
7,752-unit helper block remaining inherited.  PR-DRAFT.md lists the open
verification items.
@jwr404

jwr404 commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Independent review of the draft (James Reed, with Claude Code). Head df9e5037587ce0cfbd23c2a944515526b301e820.

This answers checklist items 1 and 2 and diagnoses the CI failure. Items 3 and 4 (helper disjointness, idle role-rank) and the word replay were not checked. Nothing here endorses a selected-frontier change.

1. Compiler majorant: wrong constants, but fixable, and the κ survives this step

power_majorant_comparison in higher-moment-strictification/verify.py is not a unit-independent function. It hard-codes the p7 unit's geometry:

  • h = 1/7;
  • B = (4+7h)v;
  • debt = 1 + 7v(1−z0);
  • the check H0 ≥ 7v.

#4416's derivation, which research/pr4416-padding-check checked independently, gets those constants from that unit's shape:

  • r_max m^h < 2^((4+7h)v) uses 10 < 2^4 (split at 10^v) and 121 < 2^7 (ambient 121^v);
  • θ = log 10 / log 11 < 6/7 licenses h = 1/7;
  • H0 ≥ 7v covers the base range n < 121^v.

The comment "changing only the new unit's ranks" refers to re-running that p7 unit at v = 150. It does not license other unit shapes.

This unit has a different shape. p19_claim.py splits at c = 20 and completes to b = 21 (the γ/δ formulas). Its invoice's largest target rank is 1 + 8·19 = 153. Every inherited premise therefore fails, checked exactly:

premise p7 (inherited) this unit
split coefficient 4 10 < 2^4 ✓ 20 < 2^4 ✗
ambient coefficient 7 121 < 2^7 ✓ 153 < 2^7 ✗
h = 1/7, i.e. θ < 6/7 ✓ 20^7 < 21^6 ✗ (θ = log 20 / log 21 ≈ 0.984)

The correct function is already in a pinned source. research/query-thinned-controllers (PROOF.md §3, verify.py::tail) treats exactly this complex shape (c = 20, b = 21, v = 1024). It re-derives the bound with:

  • h = 1/64;
  • B0 = (5+8h)·1024;
  • D0 = 1 + 8·1024·(1−z0);
  • the check H0 ≥ 8v;
  • the premises c^64 < b^63 and raw ambient ranks below 256.

Both premises hold here: 20^64 < 21^63 and 153 < 256. At tested = κ+7·gap and uniform κ+6·gap, I recomputed with exact rationals:

H0 H1
as applied (p7 constants) 497,275,706,368 4,734,066,216,450,479,105
re-derived (h = 1/64, 5+8h, 8v) 5,170,423,668,736 49,222,448,837,637,726,209
extra-conservative (ambient bound 441 < 2^9) 5,794,326,586,368 55,162,006,485,203,119,105

So the power majorant still closes, with ranks about 10× larger. Finite N is all the ledger needs, so I don't see this step killing κ = 951999/280000000. But the receipt should call the query-thinned bound, or an equivalent re-derivation, and drop the "changing only the unit's ranks" justification.

The logarithmic route remains genuinely unavailable at m = 153^1024, as the package records. That needs the η condition, which the power proof doesn't.

Not resolved here: whether the source's finite integer-batch compiler premise (FINITE-PRECOMPILATION) holds for the coded structure. That premise is separate from the constants and remains the open applicability question.

2. Tail limit: 0.97 is fine

The source argument (query-thinned PROOF.md §3) uses γ < 31/32 and δ < 19/20 only through "each bound to the power 128 is below 1/16". Then both tails at power 1024 are below 2^-32, and Bernoulli finishes with 1/(1+v·gap) + 4/2^32 < 1.

Replacing 19/20 by L = 97/100 keeps every step: 0.97^128 ≈ 0.0203 < 1/16, γ = 0.96376 < 31/32, and δ = 0.95156 < 0.97. I see no other use of 19/20 in that argument. So this is a legitimate re-instantiation, not a gap.

3. CI failure is packaging, not science

The hosted replay (research/coded-reverse-word-p19) job fails before any science runs:

missing or non-blob Git source: 7bcf2031d3eb0b53e0f3707d476fbab305b16acc:research/coded-reverse-controller/verify.py

SOURCES.json uses base_commit = 7bcf2031…, a commit on this PR branch, not canonical main. The pinned paths exist on main (e.g. research/coded-reverse-controller), so re-pinning to a canonical main commit such as ff3cc58e3… should fix it.

Small consistency issues

  • RESULT.json line 29 has "H1": 473406216450479105. The value the code produces (and the README) is 4734066216450479105, so one digit is dropped.
  • The p19_claim.py docstring (item 6) still says H0 = 171,012, H1 = 449,280, which is stale.

Reproduce my arithmetic: a ~40-line exact-Fraction script instantiating #4416's inequalities with both constant sets. I can attach it if useful.

@jwr404

jwr404 commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Follow-up (James Reed, with Claude Code). My review above left the word replay unchecked. #5349 now reports that standard(), the reference the listing is replayed against, does not equal the thinned formal controller of #4940, whose invoice this package prices. I independently reproduced its p = 2 counterexample from this PR's p19_word.py and canonical main's coded-reverse-controller/verify.py:

  • the formal controller gives diag(−1, −1, i, i);
  • the reference has off-diagonal entries.

The three causes are confirmed by reading both sources:

  • the forward-loop odd bridge direction is reversed;
  • the listing applies R at middle idles, which thinning sends to the identity;
  • idle powers count all stages instead of thick stages, at the terminal idles and also at the initial idles.

Details: #5349. So the listed word needs correcting and rebinding before the invoice can be attached to it. This is in addition to the compiler-majorant constants from my review.

@zxv

zxv commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

My agent's feedback, while attempting to integrate this work:

The p=19 draft’s current replay does not support its claimed invoice: it reuses the same nine axes at every stage while claiming targets up to rank 153, and its middle idle operations are absent from that invoice. I won’t integrate that claimed saving.

At df9e503, p19_word.py replays every LETTER/IDLE on the same range(9), while invoice() credits distinct fresh eight-axis blocks and targets up to rank 153. The middle IDLEs also execute one R each, but the invoice assigns their thinned stages rank zero. Could you bind the literal replay to fresh stage axes and recount both profiles? The current comparison establishes gauge equivalence to the same-head reference, but appears insufficient to certify the advertised supplier.

@Matarener

Copy link
Copy Markdown
Contributor

Observation on the physical binding (Mark / @Matarener, with Claude). Not a theorem; no selected-result change proposed.

Following #5349 and zxv's note, I tried to estimate what κ survives once the listing is bound to the actual native call. I believe the obstruction sits earlier than the transcription: at the terminal gauge, and the invoice has no room for it.

1. One role per pair ends with a Q-conjugated code. The retained native backward call is atomic, X ← D(X − Q C Y), Y ← D Y, with [C, DQ] = 0 but [C, D] ≠ 0, [C, Q] ≠ 0 (coded-native-caller/PHYSICAL.md). Write the physical content of each role as (gauge)·(standard content), and call a gauge cheap if it is a product of stage codes C_s^{±1} (a fixed scalar/monomial word). For the call to act as the standard reverse step, the pre-Y code must be P = C^{-1} Q^{-1} G_x Q G_y^{-1}, so G_y ≡ Q^{-1} G_x Q modulo cheap factors is forced, and after the call G_x' = D G_x D^{-1}, G_y' = Q^{-1} (C^{-1} D G_x D^{-1}) Q. Idles (other blocks' D_t) and same-parity bridges preserve this relation. So at the output one role of every pair carries Q^{-1} B_i Q, B_i the ordered product of the bank's stage codes. This is exactly the global result of coded-native-caller/GAUGE.md (odd outputs B_i D_i Q, even outputs Q^{-1} B_i D_i); I only add that no choice of cheap pre/post codes avoids it. TERMINAL.md shows Q^{-1} C Q is not a fixed scalar word (row support 4^f). For the product case I checked Q^{-1} C_1^{-1} C_3^{-1} Q on two fresh 8-axis blocks plus the central line (17 axes, width 1): every owner block has row support 48–170 (0.55–1.0 of 4·n_j), so the terms do not cancel.

The p19 listing avoids this only because it applies the full R = DQ as the stage letter, which commutes with C. The native call applies D; the extra Q per owner-role per thick stage is a rank-1 Gaussian job, and it is not in the invoice.

2. The invoice cannot pay for any of it. With the PR4929 profile, the p19 moment margin at c = 0 is 2016 rank-mass units out of 265,533. Exact census, float root:

outcome for the 19 coded output banks κ
not admitted as Gaussian targets 0
decode with one paid Q per owner (2128 rank-1), then cheap B_i^{-1}, credit 8k instead of 1+8k 0
decoder charged as one rank-2 child per owner, credit kept 0
letter R instead of D (one Q per owner-role-stage, 4256 rank-1) 0

κ = 0 here means the unit no longer breaks even. For scale: 1103 extra rank-1 units bring the complex root below the 0.0034 BIT cap, 1204 bring it below the selected 0.00302015.

Script (standard library)
# kappa of the p=19 coded-reverse invoice under four terminal-gauge outcomes (exact census, float root).
from collections import Counter
H = {4: 28, 7: 7, 8: 47, 9: 326}; PROF = {1: 2201, 2: 412, 3: 510, 4: 127, 5: 40}
p, pat, thick = 19, 'I'*9 + 'T'*9, frozenset(range(1, 38, 2))
def invoice():
    full = frozenset(range(2*p+1)); T, D, outs = Counter(), Counter(), [full, full]
    for i, ch in enumerate(pat, 1):
        outs += [frozenset(range(0, 2*i+1)) if ch == 'I' else frozenset(range(2*i, 2*p+1))]*2
    for s in outs: T[1+8*len(s & thick)] += 112
    for i, ch in enumerate(pat, 1):
        D[8*len((frozenset(range(0, 2*i)) if ch == 'I' else frozenset(range(2*i+1, 2*p+1))) & thick)] += 224
    for j in range(1, p): D[8*len(frozenset([2*j]) & thick)] += 224
    for r, n in H.items(): T[r] += 19*n
    for r, n in PROF.items(): D[r] += 19*n
    D[1] += 112*(2*p+1-19); T.pop(0, None); D.pop(0, None)
    return T, D, [1+8*len(s & thick) for s in outs[0::2]]
def root(T, D):
    f = lambda c: sum(n*r**(1-c) for r, n in T.items()) - sum(n*r**(1-c) for r, n in D.items())
    if f(0) <= 0: return 0.0
    lo, hi = 0.0, 0.05
    for _ in range(100):
        mid = (lo+hi)/2; lo, hi = (mid, hi) if f(mid) > 0 else (lo, mid)
    return lo
T, D, even = invoice()
print('margin at c=0: %d of %d' % (sum(n*r for r, n in T.items()) - sum(n*r for r, n in D.items()), sum(n*r for r, n in T.items())))
print('base root', round(root(T, D), 9))
A = Counter(T); [A.__setitem__(r, A[r]-112) for r in even]
print('A  19 coded banks not admitted as targets      ', root(+A, D))
B, DB = Counter(T), Counter(D)
for r in even: B[r] -= 112; B[r-1] += 112; DB[1] += 112
print('B  paid Q per owner, then cheap B^-1, credit 8k ', root(+B, +DB))
DC = Counter(D); DC[2] += 112*19
print('C  rank-2 decoder child per owner, credit kept  ', root(T, +DC))
DD = Counter(D); DD[1] += 224*19
print('D  letter R = DQ (one Q per owner-role-stage)   ', root(T, +DD))
for lim in (0.0034, 0.00302015):
    lo, hi = 0, 10**5
    while hi-lo > 1:
        m = (lo+hi)//2; X = Counter(D); X[1] += m
        lo, hi = (m, hi) if root(T, +X) > lim else (lo, m)
    print('extra rank-1 units tolerated before root < %.8f: %d' % (lim, lo))

Scope. The gauge argument is a hand derivation from [C, DQ] = 0 and the local identities in PHYSICAL.md/GAUGE.md; the product-support check is a width-1 computation, not a proof of growth in f. The compiler points raised by @jwr404 are separate and, as he showed, not what binds. If someone can show cancellation in Q^{-1} B_i Q for these particular products, or admit coded jobs through a typed recursive product (the open question in coded-native-caller), the conclusion changes; otherwise I don't see a path from this word to κ above the frontier.

…99964)

The invoice never sees the code: invoice(p, pattern, thick, profile) takes no coding
argument, so the coded reverse was an overlay that adds cost and no price.  Two audits
showed the cost is unpayable - the physical reverse call is D(X - QCY), so the letter
is D while [C,D] and [C,Q] differ from zero, and every coded role leaves a
Q^-1 B_i Q terminal gauge: one decoder per owner per thick stage, 2128 rank-1 units
against a 1103-unit root budget.  No proper subset of coded pairs diagonalises
(p = 3, 4, 5), so the code is all-or-nothing and always costs 112*p.

This commit replaces the hand-transcribed coded listing with the controller's own gate
trace, which is replayed in the controller algebra and required to equal controller()
exactly.  At p=19 it is 241 gates (20 forward, 19 reverse, 39 stage letters, 36
retained idles of rank 198, 108 bridges, 19 swaps), it diagonalises to the standard
outputs with denominators [1], and it carries no recoding bill and no decoder.

Also corrected here: the compiler constants.  power_majorant_comparison hard-codes the
p7 unit (h = 1/7, B = (4+7h)v, H0 >= 7v), whose premises 10 < 2^4 and 121 < 2^7 fail
for a unit that splits at 20, completes at 21 and has ambient rank 153.  The
shape-correct constants of query-thinned-controllers::tail (h = 1/64, B = (5+8h)v,
H0 >= 8v) give H0 = 5170423668736 and H1 = 49222448837637726209, with 20^64 < 21^63
and 153 < 256.  The 19/20 tail guard is recorded as settled: the source uses its
limits only through the 128th-power decay, which closes at 0.97, and gamma also meets
the source's stricter 31/32.

SOURCES now pins canonical main and no longer declares the companion package, whose
only caller was a try-block that could not run without NumPy.

Claim: complex supplier 0.007578535, BIT supplier 17/5000, kappa = 951999/280000000
= 0.0033999964, +12.31% over 0.00302728823.
@DaysSky DaysSky changed the title Certify conditional kappa 0.0033999964 via the physical p=19 coded-reverse word (complex 0.007578535, BIT 0.0034) Certify conditional kappa 0.0033999964 via the p19 word without the coded overlay (complex 0.007578535, BIT 0.0034, no recoding bill) Oct 24, 2026
… compiler ranks

Physical binding is proved by a lifting lemma instead of sampled: Phi from the retained-stage
monomial ring to address operators is a ring homomorphism (distinct-axis Gaussians commute,
powers add, Phi(1) = I, and every gate kind is the Phi-image of its monomial), so the
gate-list identity lifts to address operators for every block count.  The p=2 replay stays
as a randomised control and is labelled as such.

The lemma caught a real bug: monomial selection bits are exponents, so applying one gate per
selected stage breaks multiplicativity at exponent 2.  Both scripts now use exponent powers.

Helper compatibility is discharged mechanically (the trace touches only roles 0..2p-1); the
7752 helper units stay inherited and priced.  Compiler obligations are a table: completion
and splitting discharged on this census, normalizers/owner allocation/rank-one surplus
inherited with the no-new-job argument.
@DaysSky DaysSky changed the title Certify conditional kappa 0.0033999964 via the p19 word without the coded overlay (complex 0.007578535, BIT 0.0034, no recoding bill) Certify conditional kappa 0.0033999964 via the p19 word without the coded overlay (complex 0.007578535, BIT 0.0034, zero field bill) Oct 24, 2026
@Clear1nsight

Copy link
Copy Markdown
Contributor

HANDOFF

Research discussion / PR / artifact: Delta-only independent review of the new p19_lift.py / p19_bank.py binding in #5270. The trace identity is useful progress, but the new statement that all word-specific physical obligations are discharged is not supported by these two checks.

Exact commit: 225a19a184296d12120203a1f43b981d55465241. The inherited physical source is the historical ff3cc58e370d0f678e529246f8c73e8094e18fcf snapshot named in this head's SOURCES.json; it is distinct from current canonical main.

What is established:

  1. The emitted IDLE protocol and the new address decoder disagree. p19_plain.py emits an IDLE with tuple(sel), a list of literal stage indices. For example, a terminal event at p=2 has sel=(3,4). The formal term() converts that list to an indicator vector. But p19_bank.py:98-103 uses enumerate(sel) directly, treating list positions as stage IDs. With retained stages {1,3}, it applies D_1 once, while the event requires D_3 once. The default butterfly power here is 1, not the value 4. This is also present in the actual p19 pattern: retained terminal pair17 has sel=(37,38), requiring D_37; it would decode to D_1 under this rule. The submitted bank routine itself is hardcoded to p2. The p2 pattern-I control skips terminal idles, which hides this case. The lifting script's synthetic exponent-vector checks do not consume the emitted IDLE tuples.

    A four-address exact witness suffices: restrict all other axes of each block to their +1 Gaussian eigenvector. Over F_65537 with i=256, put a=(1+i)/2=32897 and b=(1-i)/2=32641. On the displayed two-axis unit pulse, the required D_3 gives [a,0,b,0]; the decoded D_1 gives [a,b,0,0].

  2. A homomorphism for the ideal commuting D/Q algebra does not bind that algebra to the inherited native primitive at its stated price. The pinned PHYSICAL.md:20-28 gives

    F=diag(D,D) lower(C Q^-1) and B=diag(D,D) upper(-Q C),

    with C_ij=A_ij K_i^-1 K_j. The all-ones controller trace instead uses the uncoded shears. This is a real operator difference: all112 diagonal entries of the pinned CODE.json:A are zero, so C_jj=0. With only Y_j=v nonzero, the native B produces X_j=0, whereas the ideal uncoded reverse produces X_j=-D Q v, nonzero for v!=0. This is a local direct-substitution counterexample at every width, not a global no-go theorem. The source's explicit recoding identities and ordinary bill remain relevant. The fact that invoice() has no coding argument does not establish that the uncoded primitive has the same implementation and price.

What remains uncertain: Neither check rules out a new adapter, a different producer, a fully priced joint caller, or a cancellation proved for an actual physical whole word. I did not run the submitted p19 routines, the large bank replay, price engine, compiler, or a full global endpoint audit. This review does not accept a new kappa or establish a universal decoder lower bound. Earlier terminal-gauge and budget reviews retain their separate scope.

Smallest useful next task: First bind IDLE stage lists to their intended operators and add a retained-terminal control, such as p2 pattern T and the p19 pair17 event. Then exhibit the actual native implementation of the uncoded local step, or an explicit whole-word replacement proof, with every adapter, helper ownership change, ordinary operation, precision and recursive charge included. An ideal-operator lift alone is insufficient for that source-to-invoice bridge.

Reproduction command and expected runtime: The following is a minimal illustrative CODE/event calculation, run from this head with its pinned source files. The executed independent checker additionally hash-pins and AST-matches the actual emitter, decoder and retention rule; this snippet alone does not bind that protocol. Neither checker imports a submitted evaluator. Two independent root-guarded checks of the source bindings/zero diagonal and AST/event witness passed in 0.101s and 0.202s respectively, under 5s/128MiB limits. No author replay was run.

from pathlib import Path
from fractions import Fraction as F
import hashlib, json
b = Path('research/coded-native-caller/CODE.json').read_bytes()
if hashlib.sha256(b).hexdigest() != '8be7f3f073b7981ec91c6af43edff0ac8a89f4824ef6026ae758c287dd6c03d0':
    raise ValueError('wrong source CODE')
A = [[F(v) for v in row] for row in json.loads(b)['A']]
if len(A) != 112 or any(A[j][j] != 0 for j in range(112)):
    raise ValueError('native diagonal witness changed')
sel, thick = (37, 38), set(range(1, 38, 2))
required = {s: 1 for s in sel if s in thick}
decoded = {s: 1 for s, value in enumerate(sel) if value and s in thick}
print(required, decoded)  # {37: 1}, {1: 1}

Predecessor credit: DaysSky's trace and new lifting work; Dugongue's PR4929 producer; Dillon's PR4933 physical code; Cayden Burkart / SethBurkart123's PR4940 controller; Cinna Davis / 1337isnot1337 and retained native/compiler predecessors. Matarener, jwr404, zxv and #5349/#5385 retain credit for the earlier ABI, transcription, geometry and compiler reviews. This comment contributes a check against the new head and the new IDLE protocol mismatch, not a rediscovery of their earlier claims. Review by Chris R / Clear1nsight with substantial OpenAI Codex assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants