GIVENALITY rebrands Mike as Leksa with Tanzania-focused metadata and a new disclaimer posture

Seven frontend files get new metadata, a teal icon palette, and a rewritten auth-page disclaimer -- swapping upstream's "demo service, don't upload sensitive data" warning for a "production platform, verify with a lawyer" notice. Nothing to import, but the disclaimer change is worth knowing about.

brandingcompliance

Commit 73bb7e3b is a cosmetic pass across 7 files. app/layout.tsx metadata flips from app.mikeoss.com to app.leksa.co.tz; title, description, and OG/Twitter cards update to reflect a Tanzania focus. The visible wordmark and production URL in site-logo.tsx change accordingly. Column-prompt placeholder text in AddColumnModal.tsx and WFEditColumnModal.tsx swaps "Mike" for "Leksa." The MikeIcon component gets a new default palette: teal fills (#0d9488, #14b8a6, #0f766e, #2dd4bf) replacing the upstream dark-grey stack. Route paths and component names are unchanged.

The login and signup pages carry the most notable diff. Upstream says: "Mike hosted on MikeOSS.com is currently a demo service. Please do not upload, submit, or store sensitive, confidential, privileged, client, or personally identifiable documents." GIVENALITY replaces both instances with: "Leksa is an AI-assisted legal platform. Always verify outputs with a qualified legal professional before relying on them."

The upstream wording frames the product as experimental and explicitly prohibits sensitive data. The new wording frames it as a production service and shifts to a professional-verification disclaimer instead. For an evaluator setting their own disclaimer copy: GIVENALITY's phrasing is consistent with a commercial deployment aimed at paying users in the Tanzanian legal market.

So what Nothing to import -- this is product identity work. The disclaimer rewrite is worth noting if you're thinking about how to position your own deployment: upstream's "demo service" framing versus a production-oriented "verify with a professional" notice represents two different stances on liability and user expectation.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from GIVENALITY/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`73bb7e3b`	Rebrand Mike → Leksa	GIVENALITY	2026-05-14	↗ GitHub
commit body - Update metadata, title, description, URLs to leksa.co.tz - Rename "Mike" → "Leksa" in logo, login, signup, placeholders - Update spinner icon palette to Leksa teal (#14b8a6 / #0d9488) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

SHA

Subject

Author

Date

73bb7e3b

Rebrand Mike → Leksa

GIVENALITY

2026-05-14

↗ GitHub

commit body

- Update metadata, title, description, URLs to leksa.co.tz
- Rename "Mike" → "Leksa" in logo, login, signup, placeholders
- Update spinner icon palette to Leksa teal (#14b8a6 / #0d9488)

Co-Authored-By: Claude Sonnet 4.6 <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-434.md from inside the repo you want the changes in.