Sloth-ninja calls projects what lawyers call them: matters

A small language change makes JessicaOSS read more like a legal-practice product.

i18nworkflow

Sloth-ninja has replaced user-facing references to "Projects" with "Matters" across the product, including account, privacy-data and chat-facing copy.

Nothing operational appears to change: this is a terminology pass, not a new practice-management workflow. But "matter" is the familiar label for a client engagement in UK legal practice, so the product now speaks in the terms lawyers already use when discussing work, files and responsibility.

It also establishes the vocabulary for a larger matters-focused direction that follows later in this fork.

So what UK-oriented firms and legal-product teams should care because familiar language reduces friction before any workflow change arrives.

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
`3111db6e`	WS7: rename Projects to Matters in user-facing copy	sloth-ninja	2026-07-19	↗ GitHub
commit body String-only rename of the workspace concept across all user-facing strings: sidebar nav, headings, breadcrumbs, modals, empty states, filter/column labels, aria-labels, toasts, privacy-data dialogs, and backend error details ("Matter not found", share/target phrasing). 99 strings across 27 files. Deliberately unchanged (hard rule 8 / accepted owner trade-off): identifiers, /projects route paths, DB names, log tags, comments, LLM-internal prompt text, and the "Project Finance" practice area. Terminology decision logged as R10 in docs/LEGAL_LANGUAGE_REVIEW.md for solicitor sign-off; BUILD_LOG entry added. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
`13aaf3a7`	Merge pull request #23 from Sloth-ninja/ws7-matters-rename	Ezana.H	2026-07-19	↗ GitHub
WS7: rename Projects to Matters (user-facing copy)

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

⬇ Download capture-thread-857.md