Gadoes stops dispumike asking the same legal database twice

A new caching layer means repeated research queries hit memory instead of re-fetching the same case law every session.

searchinfrastructure

Gadoes added a results cache that sits in front of the outside legal sources the fork queries - places like CourtListener (a US case-law database), EUR-Lex (the EU's official legal portal) and a handful of investment-arbitration archives. Ask the same question twice and the second answer comes back instantly, without another round trip.

The smart part is freshness tuned to the source. Court opinion databases change constantly, so their answers are held for only an hour. EU regulations and arbitration awards barely move, so those are held for a full day. There's also a tidy-up step that treats messy variants of the same query - extra spaces, a stray full stop, different capitalisation - as identical, so near-duplicate searches still share a cached answer.

So what Worth a look for anyone running a fork that hammers the same case-law sources repeatedly - faster results, lower API load, without going stale.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from Gadoes/dispumike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`19dfc0a4`	Chunk 17: Caching Layer (queryNormalizer, CacheManager, migration 004)	Gadoes	2026-05-02	↗ GitHub
`2affe555`	Merge Chunk 17: Caching Layer	Gadoes	2026-05-02	↗ GitHub

SHA

Subject

Author

Date

19dfc0a4

Chunk 17: Caching Layer (queryNormalizer, CacheManager, migration 004)

Gadoes

2026-05-02

↗ GitHub

2affe555

Merge Chunk 17: Caching Layer

Gadoes

2026-05-02

↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-25.md from inside the repo you want the changes in.