Sloth-ninja formalises when agents can merge

The fork now puts its trust model for AI-assisted delivery in writing.

workflowcompliance

Sloth-ninja has set a standing rule for autonomous agent merges: a change can be merged without fresh owner sign-off each time, but only after automated checks pass, a review is complete, and the work is recorded.

This does not change what JessicaOSS does for legal users. It does make the project's delivery process easier to read. The fork is drawing a clear line between routine, evidenced changes that agents can complete and decisions that still need human involvement.

For a legal-tech buyer or contributor assessing the fork, that matters because it clarifies how much oversight sits behind the pace of development.

So what Teams evaluating JessicaOSS can better judge its governance posture alongside its product work.

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
5167f61a Hard rule 6: standing owner authorisation for agent merges (green CI + review + BUILD_LOG); refresh Current status sloth-ninja 2026-07-19 ↗ GitHub
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
7d3f12b5 Merge pull request #16 from Sloth-ninja/merge-rule-update Ezana.H 2026-07-19 ↗ GitHub
Hard rule 6: standing owner authorisation for agent merges

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

⬇ Download capture-thread-855.md