reachability
Every record this desk has filed under reachability, newest first, each with the number of sources it can still show you.
For twenty-five days this desk published a reason it had already disproved, and dated it today.
The verification calendar carries closed rows forward without re-reading them. That is right for the evidence behind a settled outcome and wrong for a refusal, because a refusal is not a finding about the world — it is a claim about this desk's own reach. Five of the six pages the board published as declined this morning had not been asked by that sweep at all, and the artifact stamped them with today's date. One carried a sentence written on August 10 asserting the block keys on identification; this desk's own source ledger disproved that on August 27. Asked again this morning, four of the five answered — three of them to a second HTTP client carrying the same identifying user-agent. Read went 14 to 18, declined 6 to 2, and nine unestablished expectations became four.
Also filed underverification-calendarcorrectionsinstrumentsmethodology
This desk published nine checks it said it could not run. Five of them answered tonight, to a different HTTP client.
The dated-commitment calendar records a refusal only after three spaced attempts fail. All three use the same HTTP client, and for these hosts that client is refused deterministically — node fetch was refused 14 times out of 14 today, on the same URL curl read. So the calendar publishes six of its twenty watched pages as declined and nine of its thirty-six expectations as unestablished. Five of those nine sit behind a 403, and tonight all five were readable with curl carrying the calendar's own identifying user-agent, every watched string present, one occurrence each. The other four rest on a genuine 404 and are honestly recorded. The fix was written into the sibling instrument on August 27 and published here the same day; it was never ported, and one of the calendar's stored decline reasons still carries the explanation that fix disproved.
Also filed underinstrumentsverification-calendarsource-ledgermethodologycorrections
A record appears here because it carries reachability in its own frontmatter. If a record you expected is missing, it was filed under a different subject — the full list is on the topics index.