USR-2026-0036 · Discreteness
No discrete-clock signature: photon arrival times show no energy-dependent dispersion attributable to a fundamental tick.
PROVISIONAL
null result — no dispersion
re-run & confirmed 2026-07-09 (R0 — founder CI; independence pending)
A universal discrete clock would smear high-energy photon arrival times. The clock seam finds no such dispersion — a null, stated as a null.
Falsify-box — how to kill this claim
SURVIVED
DEAD on a >= 5 sigma detection of energy-dependent vacuum dispersion in GRB or blazar photon timing at EITHER order in E. Quadratic arm (the order the seam's own lattice derivation predicts), with the threshold taken from the claim's own script: dt = (D/c)*(1/8)*(E/E_lat)^2 with D/c = 2.6 Gpc/c = 2.675e17 s, E = 31 GeV and Fermi-LAT's ~10 ms resolvable delay give E_lat = 5.7e10 GeV (recomputed: 5.669e10), so a confirmed quadratic delay implying E_lat <= 5.7e10 GeV kills the claim on data already in hand, and any confirmed quadratic delay at a finite E_lat kills it outright. Linear arm: a >= 5 sigma nonzero linear-in-E LIV coefficient (finite E_QG) in a multi-burst GRB/blazar ensemble also kills it, because the claim's words are 'no energy-dependent dispersion attributable to a fundamental tick' and a linear detection is exactly that; without this arm the claim survives an observation that would kill its sibling USR-2026-0041 on the same photons. Named firing venues: CTA, LHAASO, MAGIC, H.E.S.S. multi-burst stacking, or a bright high-z GRB with a >100 GeV photon arriving milliseconds late. Explicitly OUTSIDE the criterion and therefore not excluded by it: a Lorentz-invariant discretization (no dispersion at all), and any tick between 5.7e10 GeV and the Planck energy 1.22e19 GeV - nine orders this probe cannot reach, as the script's own figure concedes when it notes the Planck-grid line lies below the plot floor.
Verification record — every quoted number, re-run 2026-07-09
| quantity | measured | verdict |
|---|---|---|
| discrete-clock verdict | NULL (no dispersion) | MATCH |
Provenance
script: clock_seam/run_clock_seam.py
script status: PRESENT
datasets: Fermi GRB timing · claim-scripts (downloadable from /data — run it yourself)
re-run: 2026-07-09
script status: PRESENT
datasets: Fermi GRB timing · claim-scripts (downloadable from /data — run it yourself)
re-run: 2026-07-09
Status, honestly
R0 pass 2026-07-09 (null result) | kill test added by the 2026-07-26 sweep. Status here is computed from evidence — the author cannot set it, and neither can we. Independent reproduction would move it; nothing else will.
§ Figures
3 from clock_seam/run_clock_seam.py
What this claim's own script draws. These are the founder's committed outputs — the same plots the script regenerates on any machine that runs it. You can redraw them yourself below.
§ Reproduction
run_clock_seam.py
Two runs of the same script — mine, and one you can start right now. A match proves the result is reproducible; it is still R0 on this registry's independence rings — same code, so it cannot move a status. Only an outside run does that.
A · Recorded
founder's machine · 2026-08-02
Probing the clock seam (lattice dispersion / speed-of-light) ...
wrote clock_dispersion.png
wrote clock_propagation.png
wrote clock_reach.png
VERDICT — the clock seam:
* A finite update rate forces DISPERSION: v_g/c = cos(ka/2) < 1, a quadratic
energy-dependent speed of light. That is a hard, unavoidable trace of any
naive space-time grid.
* It IS being hunted — GRB/blazar photon timing (Fermi-LAT, MAGIC, H.E.S.S.).
* Result: NO dispersion detected. The quantum-gravity scale is pushed to
~Planck energy (linear models) and ~10^10-10^12 GeV (quadratic). So a naive
grid coarser than that is RULED OUT. Null — like the spatial lattice.
* Honest ceiling: energy-dependent speed is also predicted by non-simulation
quantum-gravity (doubly-special relativity, some loop states). A detection
would be a discretized-spacetime signal, not a proof of simulation; and a
Lorentz-invariant discretization (or a Planck-fine grid) leaves no trace.
B · Yours
Press Run it to execute this script in your own browser — real CPython, numpy and matplotlib compiled to WebAssembly. Nothing is sent to us; it runs on your CPU. First run downloads the runtime (~5 MB), then takes a few seconds. The script runs unmodified: every number printed here, and every figure it draws, is computed on your machine. The figures appear below.
Figures your run produced
Sends only: script name and hash, the verdict, the line counts, how long it took, and your
browser and OS family. No IP is stored (it is hashed), no fingerprint, nothing you typed.
Your machine is hardware we don't own, so your run tests whether this result depends on the
computer it was computed on — a question the registry cannot answer alone.