Gadoes wires Mike to bail on a failing source fast

When an outside data source starts misbehaving, the fork now cuts it off instead of waiting on it.

infrastructureintegration

Mike pulls from external sources to answer questions. Gadoes has added a safety valve: if one of those sources fails three times in a row inside a minute, the fork stops calling it and immediately tells the interface that the source is unavailable - rather than leaving the user staring at a spinner while a dead connection times out over and over.

It's a sensible reliability move, but the trigger is aggressive. Three strikes is easy to hit: one slow network patch or a brief outage at the source can trip it, and from the commentary it isn't clear how quickly the source is allowed back in. Anyone adopting this should sanity-check whether three failures matches how reliable their own sources actually are. The same change also clears out a pile of development scratch files that had been committed by accident.

So what Worth a look for teams running Mike against multiple external legal data feeds, where one flaky source shouldn't stall the whole answer.

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 Gadoes/dispumike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
e29591ef chore: remove internal planning files and fix missing circuit breaker Gadoes 2026-05-02 ↗ GitHub
commit body
- Remove .claude/skills (internal AI tooling, not project code)
- Remove data/ (specs, mockups, roadmap - internal planning docs)
- Gitignore .claude/, data/, docs/ to prevent future re-addition
- Add missing circuitBreaker.ts and circuitBreaker.test.ts (were
  untracked since Chunk 18 - clientManager already imported them)
- Redact duplicate/real Supabase URL from backend/.env.example
- Fix EUR-Lex region glyph EU·27 → 🇪🇺 in migration and server config

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

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-29.md from inside the repo you want the changes in.

⬇ Download capture-thread-29.md