Sloth-ninja removes a firm-setup trap from JessicaOSS

A small setup rewrite eliminates the copy-and-paste mistake that can stop a new firm configuration cold.

workflowinfrastructure

Sloth-ninja has tightened the setup guidance after a firm owner pasted a placeholder identifier literally and hit a database error. The revised process removes an awkward handoff between creating an organisation and adding its initial records.

  • One repeatable setup step now creates the organisation if needed and fills in its required starting records, without asking the user to copy an identifier between steps.
  • The guidance makes the one remaining manual replacement explicit, and records the earlier error so others can find the fix quickly.

This is documentation rather than product functionality, but it makes first-time configuration less brittle and safer to rerun.

So what Teams evaluating JessicaOSS for a firm deployment should care because smoother setup reduces avoidable implementation friction before anyone reaches the legal workflow.

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
8019489c FIRM_SETUP: self-resolving seed SQL, kill the ORG_ID placeholder trap sloth-ninja 2026-07-22 ↗ GitHub
Owner hit 22P02 pasting the placeholder literally; Steps 2-3 are now one
CTE with no hand-substitution, and Step 5 spells out its one real
substitution explicitly.

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

⬇ Download capture-thread-1159.md