x402 endpoint readiness: zlv402.wreckbots.io — broken — 0 of 4, W33–W36

broken — 0 of 4, W33–W36 — most recent signed observation (round or paid refresh) is not_ready or unreachable. The rule and every tier are at /criteria; the rows are below. Never a ranking, and never a verdict without its derivation and denominator beside it.

Latest observation: not_ready on 2026-09-01T13:27:08.998Z. Rounds since first sighting: 4; probed: 2; missed: 2 (our coverage of this host: 50%). Our own coverage was suspect somewhere in the window, which the tier already reflects.

Every round, including the ones we missed

A missed week is a fact about us, not about the door. Gaps by reason: before_first_sighting 1, listed_not_walked 2.

Payment address

{"week":"2026-W36","sequence":5,"digest":"a69a2144fb5b0feee0da1003d6356dca331ccf58917e6f136ff369706d9f3722","captured":false,"not_captured_reason":"The round that last observed this door captured no payment address — the door served no parseable offer, or the round predates address capture (2026-08-20). Absence of the fact, not a fact of absence.","shared_wallet_caveat":"A shared receiving address is a fact about the address, not a verdict about operators: custodial wallets, platform checkouts and facilitator-managed payTo addresses make unrelated doors share one address. This store publishes the observation; the inference is yours to make, and yours to defend."}

What this cannot see

• Anything between rounds. The cadence is weekly, so a host that broke on Tuesday and was fixed by Saturday is invisible here and always will be.
• Why a verdict changed. We record what a probe saw, never the cause.
• Whether an absence is the host's doing or ours. That is what `gap` is for: read the reason, not the blank.
• A bare figure, and this is a refusal rather than a limitation. Dividing rounds-ready by rounds-probed and printing the quotient alone would be a verdict without its derivation, which the house sentence forbids. Every dated observation is here; a derived reading of them is published elsewhere only with its rule, its denominator and its rows.
• Anything before the corpus started. The chain is the record, and it does not reach back further than its first entry.
• Listing history before the population register existed. `listing` began with the population layer, so on rounds older than the register the timeline can only draw on the chain — and the chain only records the hosts a round WALKED. A `not_listed` on one of those rounds may be an unrecorded listing.
• Whether a host listed on the register's first day had been listed earlier. `first_seen` is when the register met it, not when the world did.

Check it yourself

The free preflight runs the same battery on any door right now: POST https://scvd.store/api/preflight/v1 with {"url": "https://zlv402.wreckbots.io/…"}. The signed rows behind this page are at /corpus/host/zlv402.wreckbots.io.json; every entry links the snapshot it came from and the chain at /corpus.json. If you operate this host and want the page withdrawn, the notice desk is the door. Corrections: /corrections.