SegPar rebrand: mike becomes IgnIA, scoped to Mexico's MASC mediation law

SegPar's fork declares its product direction in a single commit: rename everything from mike to IgnIA, shift the color palette from blue to gold-on-purple, and stake out a niche as an AI assistant for MASC mediators in Mexico. No functional changes; identity only.

brandingpersonas

The rename is mechanical but thorough. Package names, R2 bucket default, system prompt, DOCX tracked-change author field, and change ID prefix all flip from mike/Mike to ignia/IgnIA across 77 files. The new visual identity runs through globals.css: primary color changes from #0088ff to #c9900c, dark-mode background from near-black to deep purple #1a1025.

One structural note: mikeApi.ts (817 lines) was duplicated as igniaApi.ts with all Mike* type names renamed to Ignia*. The original file was left in place. Both coexist in the repo after this commit. If you're pulling any frontend component from this fork, check which API file it imports - there's dead code here that will cause confusion.

Two stub files appear - backend/src/lib/kleros/index.ts and backend/src/lib/rag/index.ts - each containing only TODO comments. The real implementations follow in the next commit. Attribution to willchen96/mike is kept in the README footer.

The .gitignore has .next appended four times. Harmless, but it indicates this commit was assembled without reviewing the file's current state.

So what Skip unless you're building specifically for Mexican MASC mediation and want the branding as a starting point. The dual-file situation (both `mikeApi.ts` and `igniaApi.ts` present) is the one thing to clean up before building on this commit.

View this fork on GitHub →

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

Commits in this thread

1 commit from SegPar/ignia, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
9bf804ca Session 1: rebranding Mike OSS to IgnIA SegPar 2026-05-07 ↗ 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-174.md from inside the repo you want the changes in.

⬇ Download capture-thread-174.md