ranade-oss makes legal-source search less likely to fail quietly

This is a reliability pass on the connectors behind legal research, with clearer limits and fewer dead-end requests.

integrationworkflow

ranade-oss has tightened how several public-law sources are checked and retrieved, so scheduled monitoring follows the same route users would rely on in practice.

  • A2AJ searches now follow the current service rules, including its 50-result limit.
  • Ontario e-Laws and Justice Laws checks now test the full find-and-retrieve journey.
  • CanLII, a Canadian legal-information service, handles limited rate restrictions without repeatedly asking for the same metadata.
  • Source references from the wrong provider are stopped early and shown as not applicable, rather than sent into a request bound to fail.

CanLII remains metadata-only and requires the user's own access key, with no scraping added.

So what Legal teams relying on multiple public sources should care because research workflows are only useful when their failures are visible and their source boundaries are respected.

View this fork on GitHub →

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

Commits in this thread

1 commit from ranade-oss/ROSS-RanadeOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
504c358b Fix Canadian connector rate-limit handling ranade-oss 2026-07-31 ↗ 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-1081.md from inside the repo you want the changes in.

⬇ Download capture-thread-1081.md