Sloth-ninja finishes JessicaOSS's public-facing rebrand

The fork now points its main public identity to the live JessicaOSS site, rather than its former MikeOSS address.

brandingsecurity

Sloth-ninja has updated the public links that shape how JessicaOSS appears when shared or visited: the site's canonical destination, social-sharing preview destination, and production logo link now lead to jessicaoss.com.

This is a small but important finishing move after the wider rebrand. It means prospective users and referral traffic land on the right product identity, while the team keeps the remaining signup legal links unchanged until approved terms and privacy pages exist. Public signup remains disabled and the pilot is invite-only in the meantime.

So what Legal-tech teams watching JessicaOSS should care because the fork is moving from a renamed codebase toward a coherent, controlled public product presence.

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
`05d56a47`	Switch live site URLs to jessicaoss.com (metadata, OG, logo href)	sloth-ninja	2026-07-19	↗ GitHub
Signup terms/privacy links deliberately left: no legal pages exist yet; pilot needs solicitor-approved AGL terms/privacy first (BUILD_LOG). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

SHA

Subject

Author

Date

05d56a47

Switch live site URLs to jessicaoss.com (metadata, OG, logo href)

sloth-ninja

2026-07-19

↗ GitHub

Signup terms/privacy links deliberately left: no legal pages exist yet;
pilot needs solicitor-approved AGL terms/privacy first (BUILD_LOG).

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