jrklaus8 is building a Canadian Mike beside the original, not inside it

The fork opens with a whole separate backend aimed at Canadian case law, citations, and data sovereignty - running alongside Mike rather than plugged into it.

infrastructurecompliance

This is the opening move of jrklaus8's Canada-focused fork, and it sets the tone for everything that follows. Rather than reworking Mike's existing engine, the team dropped an entirely separate backend next to it - one built around Canadian needs: pulling from the country's public case-law databases, checking that legal citations actually hold up, and running law-society-style compliance audits with an eye on keeping data in-country.

The catch, and it's a real one: this new layer lives beside the original system, not within it. The two stacks duplicate the same plumbing - sign-in, search, prompting - and aren't wired together. So what exists today reads more as a parallel blueprint for a Canadian Mike than a working, integrated product. Promising direction, early days.

So what Anyone weighing a Canada-first legal-AI build should watch this fork for the ambition, but click through to the code before assuming the pieces actually connect.

View this fork on GitHub →

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

Commits in this thread

2 commits from jrklaus8/mike-Canada, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
60a3c9ca Initial commit for MikeOSS Canada fork MikeOSS Bot 2026-05-22 ↗ GitHub
d87b9848 Resolve README conflict and merge original codebase MikeOSS Bot 2026-05-22 ↗ 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-538.md from inside the repo you want the changes in.

⬇ Download capture-thread-538.md