Sloth-ninja closes the loop on firm AI controls and deletion governance

The JessicaOSS fork has finished and deployed its latest review cycle, with one production database step still outstanding.

complianceworkflow

The completed work gives firms tighter control over which chat models can be used, with the server enforcing the permitted choice rather than trusting the browser. It also adds deletion governance and reverses the default failure behaviour so the safer outcome applies when something goes wrong.

Both changes were deployed on 28 July. Production still needs the accompanying database update before the new firm-level preferences and deletion controls are fully available; until then, the system is designed to tolerate the missing database fields.

So what Legal teams that need centrally enforced AI choices and more defensible handling of deletion should watch this fork, then check GitHub for the rollout details.

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

SHA Subject Author Date
35bcbb57 WS8 close-out: status refresh sloth-ninja 2026-07-28 ↗ GitHub
commit body
CLAUDE.md Current status rewritten to the completed WS8 state (#43-#46
merged + deployed 28/07); HANDOVER §3a marked resolved/historical.
Records the outstanding owner action: run migration 20260727_01 in
production Supabase.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

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

⬇ Download capture-thread-1139.md