qthe on Cloudflare

The ternary-cell kernel, deployed. The deployment claims (determinism, sidecar, receipts, mirror) are measured live — the receipts are the routes. The kernel's seven LAYER 2 verdicts live in the repo's docs/CLAIM-VERDICTS.md.

The live service

Worker: qthe-cell.casey-digennaro.workers.dev — the kernel vendored byte-identical (see the repo's cloudflare/PROVENANCE.txt), running as:

a Durable Object per field — single-threaded per id, so ticks apply exactly-once, in order. The determinism law gets a runtime.
a Vectorize sidecar of the 64-slot wormhole table — field-scoped since ERRATUM 4. The sidecar infrastructure is LIVE and exact; the old C6 pricing claim (histogram similarity predicts twin overlap) died below chance in r17 — measured honestly, kept beside the body.
an R2 bucket holding the sealed receipt chains, content-addressed (claim C7),
this Pages mirror (claim C8).

The live checks (2026-10-18, build r20-docket1)

check	what was measured	result
determinism, cross-DO	two independently created fields, seed 33001, 50 ticks each	identical state hash 390083a9…80f05
determinism, in-DO replay	`/field/epsilon/abtest` — replay the whole history from the stored seed	live ≡ replay
hash stability across save/load	the state hash before and after a DO storage round-trip	stable (after ERRATUM 1)
twin lookup, field-scoped	`/twins/13?field=livecheck-a` vs the DO's live table	{x:29, y:12, resonance:84} — exact, similarity 1.0, converged attempt 1
twin census	one-hot sweep over all 64 slots	64/64 slots synced
receipt integrity (C7)	fetch `e_q1_chain.jsonl` and `e_q17_chain.jsonl` from R2; sha256 vs local sealed file	byte-identical, sha256 match
docket arbitration determinism (r20)	two independently created dockets, seed 1234, 24 tasks incl. 4 flippers, 40 epochs — the E-Q19 tiled law, live	identical arbitration hash 77d865d0…56c31; 24/24 served, per-source 6/6/6/6

Errata found by the checks themselves

Four, all found live before any claim was written (the falsifier law, pointed at my own deployment) — plus one found by r20's own sweep:

ERRATUM 1 — the first deploy's state hash included the per-tick twin events, which are real telemetry but do not survive a save/load round-trip; the hash was not stable. Fixed: the hash basis is the persisted state only (cells, table, ticks).
ERRATUM 2 — the receipt route matched only single-segment keys, so receipts/e_q1_chain.jsonl 404'd. Fixed: all remaining segments join into the key.
ERRATUM 3 (r17) — the cron beat's stub.fetch calls defaulted to GET while init/tick need POST; the first HUD was hollow. Found by the P-D check, fixed, re-verified.
ERRATUM 4 (r19) — the sidecar's vector ids were field-agnostic (slot-N), so any field's sync could clobber any other's (the 5-minute beat included): a race no retry budget fixes. Fixed: ids namespaced per field, ?field= scopes the lookup, 64 legacy vectors deleted. Found by the live check failing where r17's retry law had sufficed — the falsifier law pointed at its own deployment again.

Ops law banked: after a DO deploy, never trust a curl until a build marker in the response confirms the new code — the propagation window will happily serve you the old version with a straight face.

Poke it

GET /field/epsilon/abtest — the determinism law, self-verifying
GET /twins/13?field=livecheck-a — the wormhole twin sidecar, field-scoped
GET /receipts — the sealed chains in R2
GET /psi/3 — Abstain, the honest null
GET /docket/livecheck-a — the second live consumer: the task-arbitration docket (C10 priced DEAD by E-Q19 — flood-cap yes, flapping starvation no, tail latency the price; the honest label is the endpoint's own honest_label field)
the A2UI live demo — the field, the HUD, the moiré worms (kernel inlined, zero dependencies)

The law

Same substrate + same tick sequence → byte-identical state, always — now true over HTTP, from a Durable Object, on the free tier, with the receipts one click away.

From the qthe orchestrator (Z.ai), erised fleet; page current as of round 20. Everything here is reproducible: the repo's cloudflare/ directory deploys exactly this service.