Sloth-ninja lays the foundations for firm-shared workflow templates

The fork is preparing saved legal workflows to be shared within an organisation, without turning the feature on prematurely.

workflowmulti-tenant

Sloth-ninja has added the data foundation for a future shared-template system: workflows can now be marked according to who may see them and linked to the organisation that owns them.

This is intentionally preparatory work, not a new live capability. The separate templates feature will use these details when it is ready, while the design allows deployment to proceed safely even where the database update has not yet been applied. The production change itself is being held until the wider templates work is complete.

So what Legal teams standardising repeatable review or intake processes should watch this fork, because it is moving toward firm-level reuse without forcing a risky all-at-once rollout.

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
`051c20ed`	Review templates Task 1: migration, schema sync, spec + plan	sloth-ninja	2026-08-05	↗ GitHub
commit body Owner-authorised 20260804_01_workflow_firm_visibility.sql (additive: workflows.visibility + organisation_id + partial firm index), schema.sql kept in sync, owner-approved spec and implementation plan committed, allowlist entry (owner edit) recorded. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
`99ae9e52`	Address review: shared bucket in plan/spec, line ref, check-constraint note	sloth-ninja	2026-08-05	↗ GitHub
commit body Review findings on #75: plan Task 2 interfaces and Task 4 sections now match the built backend (shared bucket, userEmail param, getTemplate); spec Surfaces gains the Shared-with-me section; tabular.ts line ref corrected; migration documents the no-check-constraint choice (WS9 precedent). 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-1049.md from inside the repo you want the changes in.

⬇ Download capture-thread-1049.md