pdombkins turns Mike into a separate Rose product

Rose now has its own identity, domain and the beginnings of a more self-contained legal service.

brandingsecurity

This is a full break from the Mike name, not a cosmetic reskin. pdombkins has moved the fork to rose.lawyer and replaced the surrounding product identity, putting Rose on its own path from the upstream project.

The release also carries a few practical changes:

Legal terms and privacy pages, plus a library area for legal resources.
Tighter approval checks before people can access Jade.
Group invitations sent through Resend, an email-delivery service, instead of a rate-limited provider.

The name change will matter less to users than those access and invitation details, but the scale of the rebrand signals a fork becoming an independent product.

So what Legal teams assessing Rose should treat it as its own product with its own operational choices, then inspect GitHub for the access and collaboration details.

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 pdombkins/rose_lawyer, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

2a6bcc62 Rebrand to Rose, rose.lawyer domain, and feature backlog Peter Dombkins 2026-07-25 ↗ GitHub

SHA	Subject	Author	Date
`2a6bcc62`	Rebrand to Rose, rose.lawyer domain, and feature backlog	Peter Dombkins	2026-07-25	↗ GitHub
commit body - Rebrand from Mike OSS / Mike (Australia) to Rose across app, docs, and env - Point rose.lawyer at the Cloudflare Worker; migrate DNS to Cloudflare; Resend domain verified for email - Add Terms of Use and Privacy Policy pages (/terms, /privacy) - Fix README: schema.sql staleness note, Moonshot/Kimi provider mention, correct CourtListener as inactive/legacy (not wired to assistant tools) - Agent runtime, notifications, audit/RBAC, knowledge base + playbooks, MCP server, Regwatch, tabular v2, clauses, admin analytics, exports, Moonshot/Kimi provider, usage/budget tracking, Lists, bulk CSV import - Legal resources library tab; fix Jade access-approval gating gaps - Group invite delivery via Resend instead of Supabase's rate-limited mailer - Ignore .fuse_hidden* mount artifacts
`6b4ca55f`	Fix repo URL in CLAUDE.md	Peter Dombkins	2026-07-25	↗ GitHub

commit body

- Rebrand from Mike OSS / Mike (Australia) to Rose across app, docs, and env
- Point rose.lawyer at the Cloudflare Worker; migrate DNS to Cloudflare;
  Resend domain verified for email
- Add Terms of Use and Privacy Policy pages (/terms, /privacy)
- Fix README: schema.sql staleness note, Moonshot/Kimi provider mention,
  correct CourtListener as inactive/legacy (not wired to assistant tools)
- Agent runtime, notifications, audit/RBAC, knowledge base + playbooks,
  MCP server, Regwatch, tabular v2, clauses, admin analytics, exports,
  Moonshot/Kimi provider, usage/budget tracking, Lists, bulk CSV import
- Legal resources library tab; fix Jade access-approval gating gaps
- Group invite delivery via Resend instead of Supabase's rate-limited mailer
- Ignore .fuse_hidden* mount artifacts

6b4ca55f Fix repo URL in CLAUDE.md Peter Dombkins 2026-07-25 ↗ GitHub

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

⬇ Download capture-thread-932.md