Sloth-ninja gives JessicaOSS a firm-level control plane

This fork lays the groundwork for running the legal-AI product by organisation, not just by individual user.

multi-tenantworkflow

Sloth-ninja has introduced the core structure for organisations, with an administrator role and the profile information needed to connect people to a firm. It is a foundational move: later work on firm access, policies, usage visibility, integrations and deletion controls can now attach to a shared organisational boundary.

Just as notably, the database change was explicitly authorised through the project's migration-governance process. That suggests the team is treating firm-level separation as a consequential operational change, rather than a quick feature toggle.

For legal teams evaluating shared AI tooling, this is the difference between individual accounts and a system that can begin to reflect how a firm or legal department is actually managed.

So what Managing partners, legal-ops leads and product founders should watch this fork if organisation-level access and governance matter to their deployment model.

View this fork on GitHub →

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

Commits in this thread

4 commits from Sloth-ninja/JessicaOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
a1e39646 WS8 PR A: organisations, admin role, profile plumbing sloth-ninja 2026-07-22 ↗ GitHub
commit body
Foundation for firm administration. Adds the organisation (firm) entity, an
admin/member role on user_profiles, firm-level shared API keys, backend
resolution + a requireAdmin guard, and profile plumbing to the frontend types.
No gating behaviour - policy flags are present but unconsumed; self-hosters with
no organisation keep the existing per-user behaviour everywhere.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
69c5e5c1 Record owner's migration authorisation for 20260721_01_firm_administration.sql sloth-ninja 2026-07-22 ↗ GitHub
Content authored by the owner in the allowlist (human-maintained file);
this commit only records it in history. No agent edit.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
7b52673c Merge pull request #35 from Sloth-ninja/commit-migration-allowlist Ezana.H 2026-07-22 ↗ GitHub
Record owner migration authorisation (allowlist)
d52ffc01 Merge pull request #34 from Sloth-ninja/ws8-org-foundation Ezana.H 2026-07-22 ↗ GitHub
WS8 PR A: organisations, admin role, profile plumbing

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

⬇ Download capture-thread-866.md