Edu-Carone-SA puts tenant walls around Mike's client data

This fork adds database-level checks intended to stop one organisation from seeing another's work.

securitymulti-tenant

For a legal-AI product handling client documents, tenant isolation cannot rest on the application behaving perfectly. Edu-Carone-SA has added access rules across the product's database, backed by a defined tenancy model and tests that try to cross the line between users and organisations.

The work covers the whole data store, with 82 access policies across 25 tables, plus checks for which routes require which level of protection. There is also a verification step and a rollback path, which matters when security controls need to be audited or reversed safely.

The fork's production release remained blocked by a separate AGPL licensing question. That does not change the value of this security work, but it does mean prospective adopters should assess the licensing position too.

So what Managing partners, GCs and legal-product teams should care if they need credible separation between clients in a shared AI workspace.

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

SHA Subject Author Date
505a3689 MIKE-03: Authorization, tenancy and Row Level Security EduardoCarone 2026-07-10 ↗ GitHub
Sprint 3: RLS on all 25 tables (82 policies), tenancy model, route classification, 82 new tests. KNOWN_SECURITY_BLOCKER removed. Production BLOCKED (AGPL pending). READY for Sprint 4.

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

⬇ Download capture-thread-963.md