#2 THE READER, built to C's §8 ruling (direct wire, no hook) and to what the waves measured,
not to the brief's letter:
· `pack.gone` set, `price` updated IN PLACE — items[] never added to, removed from, or
reordered, because its identity AND ORDER are the pick's stability (C §8.3). Filtering the
array instead reshuffles the crate: C measured ONE sale changing 21 OTHER records.
· fire-and-forget at room build, 1200ms abort, etag-cached, circuit-broken on first failure.
The dig never blocks on the network (charter risk #1). No await anywhere near the door.
· fires ONLY for a real-sourced shop. G's fence 404s a mint shop, and asking anyway would be
R26's blind probe wearing a server. The manifest already knows which is which.
TIER 2 IS OPT-IN (`?live=1` / `?live=<url>`; absent → byte-identical to the beta). That is the
R26 lesson applied to a server: a default boot that probed for a GODVERSE host would ask a
question with no answer on every machine that isn't John's. Tier 2 is a place you go, not a
thing that happens to you. Auto-discovery is a v5.x question with a reachability contract.
PROVEN IN THE BROWSER (formal smoke class still to land):
· sold-means-gone, via G's make-fixture (production `gone` is EMPTY — 0 sales since
2026-07-01 — so a live assert would pass vacuously forever; G built the subject before the
gate could be born blind): 3 sold → gone[3] → items[] 120→120 IDENTITY AND ORDER INTACT,
117 survivors, COLLATERAL 0. C called this: both pick-then-omit and filter-the-array hide
the sold record, so "the gone item never renders" cannot tell them apart — the obvious
assertion is vacuous and goes green. Collateral is the one that discriminates.
· KILL THE SERVER MID-SESSION → enter took 13.1ms, worst frame gap 14ms, the crate still
renders its own 120 real covers, and ZERO console errors. Charter law #1 proven by
execution instead of assertion — the thing A correctly refused to retire from the risk
list until this gate went green.
Recorded, not hidden: after a mid-session kill the etag-cached `gone` persists for the session,
so a killed server does not resurrect sold records mid-walk. That is tier-1-plus-last-known, not
tier-1-exactly. It is the honest behaviour (a network blink must not re-stock a shop) and a
server-down BOOT is still pure tier 1 — but it is a nuance the brief's "degrades to tier 1
exactly" doesn't cover, so it goes in writing rather than in the gaps.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
39cfc3d3ed