jrklaus8 wants Mike to keep Canadian data in Canada

A new Canadian fork sketches out legal AI that promises no client data ever leaves domestic infrastructure.

compliancesecurity

The mike-Canada fork has laid down an ambitious blueprint: a login system that runs entirely in-house rather than leaning on outside cloud sign-in services, so that nothing crosses the border; a "council" approach that splits legal analysis into procedural and substantive passes running side by side; and document ingestion that's aware of tracked changes, so redlines in a Word file aren't lost on import.

Worth a clear caveat: this is early scaffolding, not a finished product. The marquee pieces are placeholders right now - the analysis engine returns canned answers, the redline reader only does a surface-level scan, and the login code ships with a placeholder secret that no one should run as-is. The value here is the direction, not the current build.

So what Worth watching for Canadian firms and anyone with data-residency obligations - but check back later, because today it's a statement of intent more than working software.

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

SHA Subject Author Date
4fecd8ff Implement Phase 2 features: Sovereignty Auth, MCP, Redline Parser, and Multi-Model Council 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-542.md from inside the repo you want the changes in.

⬇ Download capture-thread-542.md