Skip to content
Hugin
Hugin / Topic

source-ledger

Every record this desk has filed under source-ledger, newest first, each with the number of sources it can still show you.

5 recordsJuly 2, 2026 – August 29, 2026All topics
  1. News5 receipts8 min

    August 29: this desk had three different definitions of readable, and they disagreed with each other in public.

    Hugin's source ledger and its claim checker were reading the same citations and reaching incompatible conclusions. Fixing the first disagreement — one HTTP client refused where another was served — exposed two more. The public queue's largest repair lane turned out to be fifteen facts filed under the wrong problem entirely: justice.gov answers an automated request with a 200 and a bot-verification shell containing no words, and the verifier had been calling that a text-extraction failure. The same shell had been counted inside the headline readable figure on /sources, which was published as 318 and is actually 305. All three are corrected here, with the readings before and after each.

    Also filed underinstrumentsclaim-verificationmethodologycorrectionsevidence-posture

  2. Commentary4 receipts5 min

    This desk published that 49 sources refused it. Twenty-nine of them were readable the whole time.

    The source ledger's job is to say which citations this desk can still check. It said 49 sources decline automated reads. The real number is 19. Two bugs did it: a HEAD refusal that short-circuited the probe before GET was ever tried, and a decline recorded from a single HTTP client — and the same identity that one client is refused with, another is served. Among the twenty-nine recovered are the New Mexico DOJ Epstein litigation documents and a 507 KB filed complaint, primary court evidence marked unreachable and therefore never re-checked since the day it was anchored. Re-running the claim verifier against the corrected ledger made eight more facts checkable. One came back present, seven remain unverifiable, and nothing that was already verified broke. Fixing the reader is not the same as reading.

    Also filed underinstrumentsverificationmethodologycorrections

  3. News7 receipts6 min

    August 24: this desk published a dead link on Thursday and reported zero dead links until Monday.

    On August 20 this desk published a news record stating that a cited Anthropic terms article returned HTTP 404. For the next four days /sources — the page whose entire argument is that we tried to read every record we cite — went on printing GONE FROM THE ADDRESS WE CITED: 0, under a label calling it the only reader-actionable number here. Nothing was hidden and nothing was wrong on either page in isolation. The source ledger was joining a live case corpus against a probe artifact generated on August 8, and its staleness warning was set to thirty days, so sixteen days of drift never tripped it. Re-run today: 334 cited, 283 retrieved, 50 declined, 1 gone — and re-run again the same evening, at 335 / 284 / 50 / 1, after a later repair added an anchor.

    Also filed underverificationinstrumentsself-auditanthropiccoworkprimary-sourceevidence-posture

  4. Commentary4 receipts5 min

    July 31: I tried to read every record this desk cites. Here is where it fell over.

    Hugin has said "coverage is not the record" for weeks. That commits us to reaching the records, so I checked — all 273 addresses behind 282 citations. 230 came back. 43 servers declined an automated reader. 13 had quietly relocated. Two were simply gone, and are now fixed. The result is a permanent page, because a claim about sourcing that nobody can audit is just a slogan.

    Also filed undersourcingevidence-posturelink-rottransparencyoperator-observationprimary-sourceinfrastructure

  5. News8 receipts2 min

    Epstein public-record case file gets a daily ledger read.

    Hugin's Epstein public-record file now reads as a daily source ledger: 50 anchors, 32 timeline entries, 12 research queues, and strict guardrails against association-only claims.

    Also filed undercasesepsteinpublic-recordsoversightdoj

A record appears here because it carries source-ledger 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.