Sloth-ninja lays the groundwork for governed deletion and firm AI choices

This fork is putting the data controls in place before it asks firms to trust new AI and retention features.

complianceinfrastructure

Firm-level AI preferences: an opt-in setting and place to store a firm's model choices, ready for later product work.
Retention controls: administrators can set how long deleted material is kept, from 1 to 365 days, with 30 days as the starting point.
Soft deletion: projects, documents, chats, reviews and workflows can be marked for removal while staying available for the retention process.
Deletion records: each bulk deletion gets one permanent, organisation-scoped audit entry, inaccessible to ordinary browser users.

Account deletion for organisation members remains blocked in the first release.

So what Legal ops teams and risk-conscious firms should care because deletion now has a defined retention window and an auditable trail.

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

f9dd9eb7 WS8 F/G bundled migration: firm models + deletion governance sloth-ninja 2026-07-27 ↗ GitHub

SHA	Subject	Author	Date
`f9dd9eb7`	WS8 F/G bundled migration: firm models + deletion governance	sloth-ninja	2026-07-27	↗ GitHub
commit body Owner-authorised 27/07/2026 (allowlist entry added by the owner). Additive, defaulted columns only - zero behaviour change until PR F/G code lands: - organisations: allow_member_model_prefs (default false), model_config jsonb, retention_days (default 30) - deleted_at/deleted_by tombstones + pending-purge partial indexes on projects, documents, chats, tabular_reviews, workflows (document_versions precedent) - deletion_audit_logs: append-only org-scoped audit trail, RLS enabled, browser-role grants revoked schema.sql mirrored; BUILD_LOG records the gate decisions (account deletion blocked for org members in v1, retention 1-365 admin-editable, one audit row per bulk action). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

commit body

Owner-authorised 27/07/2026 (allowlist entry added by the owner).
Additive, defaulted columns only - zero behaviour change until PR F/G
code lands:

- organisations: allow_member_model_prefs (default false), model_config
  jsonb, retention_days (default 30)
- deleted_at/deleted_by tombstones + pending-purge partial indexes on
  projects, documents, chats, tabular_reviews, workflows
  (document_versions precedent)
- deletion_audit_logs: append-only org-scoped audit trail, RLS enabled,
  browser-role grants revoked

schema.sql mirrored; BUILD_LOG records the gate decisions (account
deletion blocked for org members in v1, retention 1-365 admin-editable,
one audit row per bulk action).

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

⬇ Download capture-thread-1143.md