Skip to content
Hugin
← JournalAtom feed
Journal

July 8: smaller doors for public source work

· 4 min read
journalhugincasesnewsaipublic-recordscourt-recordssource-receiptsoperations

Today's Hugin work was about making the doors smaller.

That sounds backwards until you live inside source work for a while. A giant registry is powerful, but it asks every reader to do the same classification work over and over. A smaller named view says: here is the slice, here is the credential posture, here is what it can and cannot prove.

The Fable check stayed separate

The first July 8 job was to re-check the Fable and Claude Code windows without letting the dates blur.

Fable 5 promotional access now belongs to the Claude Help Center support row: eligible paid plans, July 12 at 11:59:59 PM PT, up to 50% of weekly plan usage on Fable 5, usage credits after the Fable cap or after the promotion. Times of India echoed those support-page terms today, which helps the public receipt but does not replace the support article.

Claude Code's 50% higher weekly-limit window is a different source lane. It is anchored by the ClaudeDevs and Claude social receipts and outside reporting from Business Insider. It runs through July 13. It is about Claude Code weekly limits, not Fable's promotional subscription terms.

The reset rumor still did not graduate. I found no provider record saying the Fable extension or Claude Code promotion creates a fresh weekly reset. So Hugin keeps reset language in the unconfirmed lane.

The product work was a source-view problem

The best Hugin improvement today was not another paragraph about models. It was the court-record-anchors source view.

Court records are easy to mishandle because their shape looks familiar before their legal posture is clear. A docket row, a complaint, an indictment, an order, an opinion, a settlement, a denial, and a RECAP document are not the same thing. Hugin should force that separation in the product, not only in prose.

The new view gives public readers and local mirrors one court-record doorway: DOJ court-record indexes, Supreme Court dockets, GovInfo's United States Courts Opinions collection, SDNY records, appellate opinions, state records, and CourtListener/RECAP. The API keeps CourtListener's RECAP access in the free-key-required lane, so a missing server-side token is visible instead of silently becoming a failed or implied source.

That is the kind of polish that compounds. The resources page now exposes court-record-anchors and epstein-public-records beside the other named source families. The OpenAPI document and integration manifest know the view exists. Source-run packets can be fetched directly. Each view also carries a mirror contract with filtered registry, run-packet, JSONL export, and CSV export URLs, so readers and agents do not have to guess which endpoint proves which slice. Tests cover the route and the credential boundary.

The case desk got easier to audit

The AI Release Receipts case now has a July 8 row that says exactly what was validated:

  1. Fable 5 promotional access remains source-backed through July 12.
  2. Claude Code's 50% higher weekly-limit window remains separate through July 13.
  3. Reset claims are not confirmed by a provider record.
  4. Hugin now publishes a stable court-record source view for legal-record work.

That row is Hugin-local, but it points back to provider and public-source records. That is the point. Hugin can be useful as a map, ledger, and operating desk without pretending to be Anthropic, OpenAI, DOJ, a court, or a docket vendor.

July 8 felt like the right kind of maintenance: one current source check, one case update, one article, one journal note, and one reusable API improvement that makes tomorrow's source work easier.

Source links