📝 jrklaus8's Canada fork dresses up the demo before the data is real 2 commits 4d ago searchinfrastructure draft
The Canadian legal lookups in this fork look live, but they return canned, invented results.
jrklaus8/mike-Canada
A Canadian fork of Mike that keeps legal AI - and the client data behind it - on domestic, sovereign ground.
mike-Canada is jrklaus8's attempt to reshape Mike into a legal assistant built for Canadian practice. The throughline is data sovereignty: the fork runs a separate, homegrown backend aimed at keeping client data on domestic infrastructure, with the option to run the AI locally rather than calling out to a third-party cloud, and sign-in being pulled in-house onto a self-hosted token system. On top of that foundation it layers the things a Canadian legal product is expected to have - PIPEDA privacy notices, consent and cookie banners, Law Society of Ontario professional-responsibility framing, and an assistant nudged to speak in Canadian legal idiom and citation norms.
The assistant reaches out to live Canadian legal data sources (CanLII, CourtListener, and others) through a dedicated retrieval layer, and the chat window has been wired up to talk to that Canadian-only backend. jrklaus8 is also explicit about lineage, crediting upstream creator willchen96 (William Chen) in the project's documentation - a maintainer who wants the fork's intent and etiquette on record.
One honest caveat for anyone trying it: the product looks further along than it is. The Canadian legal lookups are dressed up in polished UI and deployment scaffolding, but several still return canned, invented results - this is a demo standing in for data that isn't fully live yet.
What's in it
- Canadian data sovereignty Built to keep client data on domestic infrastructure, with the AI able to run locally and sign-in moving onto a self-hosted token system.
- Live Canadian legal sources Connects the assistant to Canadian case-law and legal data feeds like CanLII and CourtListener instead of relying on bundled content.
- PIPEDA compliance, out of the box Ships the privacy policy, terms, consent flow, and cookie banner Canadian privacy law expects.
- Law Society of Ontario framing Wraps the assistant in Ontario-specific lawyer duties and prominent 'use at your own risk' disclaimers.
- Speaks Canadian legal Prompt-layer tuning steers the assistant toward Canadian legal terminology and citation conventions.
- Demo-stage lookups The Canadian legal results look live but are partly mock data for now - polish ahead of real retrieval.
Direction
complianceintegrationinfrastructure
Activity
📝 README architecture summary (PIPEDA, local inference, RLS, Drizzle) (no public page) 1 commit 4d ago not yet rewritten
📝 Drizzle ORM + Vercel AI SDK migration scaffolding (no public page) 1 commit 4d ago not yet rewritten
The mike-Canada fork now ships the consent furniture Canadian privacy law expects out of the box.
📝 jrklaus8 tightens who can see what - and offers an in-house AI option 2 commits 4d ago securitymulti-tenant draft
Two changes in the Canada fork: every database request now runs under the individual user's permissions, and the AI engine can run entirely on a local machine.
The Canada fork wraps the assistant in Ontario-specific lawyer duties and a wall of "use at your own risk" disclaimers.
📝 jrklaus8 wires Mike's chat window into a Canadian-only backend 2 commits 4d ago integrationsearch draft
The Canada fork just connected its front-end chat to a homegrown Canadian retrieval engine - the moment the two halves of the project finally talk to each other.
The mike-Canada fork now reaches out to live Canadian case-law feeds instead of relying on whatever's bundled in.
A small but deliberate prompt-layer tweak nudges the fork's AI toward Canadian legal idiom and citation norms.
The mike-Canada fork is moving sign-in off a third-party cloud service and onto its own self-hosted token system, in the name of keeping legal data on home turf.
📝 README attribution crediting upstream creator willchen96 (no public page) 2 commits 4d ago not yet rewritten
A new Canadian fork sketches out legal AI that promises no client data ever leaves domestic infrastructure.
📝 jrklaus8 is building a Canadian Mike beside the original, not inside it 2 commits 4d ago infrastructurecompliance draft
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.
Threads of work (detailed view)
jrklaus8's Canada fork dresses up the demo before the data is real
The Canadian legal lookups in this fork look live, but they return canned, invented results.
jrklaus8 makes the Canadian fork mind its privacy manners
The mike-Canada fork now ships the consent furniture Canadian privacy law expects out of the box.
jrklaus8 tightens who can see what - and offers an in-house AI option
Two changes in the Canada fork: every database request now runs under the individual user's permissions, and the AI engine can run entirely on a local machine.
jrklaus8 makes Mike answer to the Law Society of Ontario
The Canada fork wraps the assistant in Ontario-specific lawyer duties and a wall of "use at your own risk" disclaimers.
jrklaus8 wires Mike's chat window into a Canadian-only backend
The Canada fork just connected its front-end chat to a homegrown Canadian retrieval engine - the moment the two halves of the project finally talk to each other.
jrklaus8 plugs Mike into Canada's legal data sources
The mike-Canada fork now reaches out to live Canadian case-law feeds instead of relying on whatever's bundled in.
jrklaus8 teaches Mike to talk like a Canadian lawyer
A small but deliberate prompt-layer tweak nudges the fork's AI toward Canadian legal idiom and citation norms.
jrklaus8 starts pulling Canadian login auth in-house
The mike-Canada fork is moving sign-in off a third-party cloud service and onto its own self-hosted token system, in the name of keeping legal data on home turf.
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.
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.