qthe on Cloudflare

The ternary-cell kernel, deployed. LAYER 2 claims, each measured live on 2026-10-18 — the receipts are the routes.

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 (claim C6),
• an R2 bucket holding the sealed receipt chains, content-addressed (claim C7),
• this Pages mirror (claim C8).

The live checks (2026-10-18, build r16-fix2)

Errata found by the checks themselves

Two, both found live before any claim was written (the falsifier law, pointed at my own deployment):

• 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.

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/37 — the wormhole twin sidecar
• GET /receipts — the sealed chains in R2
• GET /psi/3 — Abstain, the honest null
• 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, round 16. Everything here is reproducible: the repo's cloudflare/ directory deploys exactly this service.