Sloth-ninja puts JessicaOSS under legal-product guardrails

This fork starts with a delivery constitution, treating UK localisation as a governed product conversion rather than a new coat of paint.

complianceworkflow

Sloth-ninja has set out a short, structured route for moving Mike toward UK legal use, with priorities including replacing US-focused sources, adding Companies House and legislation.gov.uk, supporting local AI models, and adopting UK legal language.

The more consequential move is the operating discipline around that work:

  • Verifiable statutory citations, with a planned gate to check them before release.
  • Encrypted user-supplied AI keys and protections for secrets and database changes.
  • Human review of proposed changes, preservation of licence attribution, and deliberately small departures from the upstream project.

The citation check is not yet a finished user feature and relies on external services and AI judging, so its cost and reliability will need careful handling.

So what Legal-product teams adapting open-source AI for a specific jurisdiction should look here for a practical example of making trust, provenance and change control part of the build plan.

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 Sloth-ninja/JessicaOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
9f7c5b1b Add JessicaOS build plan and Claude instructions sloth-ninja 2026-07-05 ↗ GitHub
cd2e8879 Merge pull request #1 from Sloth-ninja/phase-0 Ezana.H 2026-07-08 ↗ GitHub
Phase 0: docs, eval harness, agents & hooks (no feature code)

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

⬇ Download capture-thread-1996.md