Today was a good reminder that a public evidence tool has to be calm when the public web is not.
A Reddit link scan hit the rough edge: hosted fetches can get blocked upstream. Reddit has been aggressive about anonymous cloud traffic, and a 403 from that side does not mean the reader did anything wrong. It usually means the hosted scanner could not get a clean path through Reddit's public endpoint from the server it is running on.
Hugin already has recovery paths for that world: share-link resolution, Atom fallbacks, old Reddit/profile fallbacks, archive fallbacks, and a companion path for fetching from the reader's own browser context when Reddit refuses a data-center request.
But the July 5 issue exposed a smaller under-the-hood problem: when a Reddit post had recent duplicate reports, the direct scan route only checked one cached row before deciding whether to hit Reddit again.
The useful fix
The right behavior is boring in the best way.
Before Hugin asks Reddit for the same post again, it now checks a short window of recent reports for that post ID. If any recent report is still fresh and has the current hosted fallback receipts, Hugin returns that report as cached. If the recent reports are genuinely stale or missing the current fallback coverage, then it can rescan.
That means a report with limited author context can still be valid. Limited is not the same as failed. The question is whether Hugin already tried the right fallbacks and recorded that source posture.
Why this belongs in the public desk
This is the kind of thing I want Hugin to be honest about. A scanner should not pretend every source is equally reachable from every server. It should say what it could read, what was blocked, which fallbacks ran, and why a reader is seeing a cached report instead of a duplicate.
The July 5 news update says that out loud. The AI Release Receipts case file now carries the operational record too, because the model/tool conversation is not only "which system is strongest." The real builder stack is the combination that lets an agent find the route, patch the behavior, update the public receipts, and verify the contracts.
Codex feels very good for that lane. Fable can still be great for the broad second read and infrastructure cleanup. The working stack is both: the big context that shapes the map and the agentic local loop that keeps the map walkable.
What changed today
- The Reddit analyze route now checks recent reports for the same post ID before making another hosted Reddit fetch.
- The store layer exposes a bounded recent-report lookup so duplicate reports can be evaluated newest-first.
- The regression test covers the case where the newest duplicate is not reusable but another recent report has current fallback evidence.
- The news, journal, and AI release receipts case file now name the July 5 recovery pass as a public operating receipt.
That is the Hugin posture I want: fresh, useful, and not dramatic about normal web friction.