🟢 #2 docs: Lexnova AI design briefs (full set) +2,207 2mo ago self by
vincentbirot ↗ analysis ↗ GitHub Adds the complete design specification set for the Lexnova AI product roadmap.
vincentbirot/lexnova-mike
Mike fork targeting law firms: legal vocabulary, a full seven-sprint product roadmap, and an agentic build pipeline.
vincentbirot/lexnova-mike is a fork of willchen96/mike aimed squarely at law-firm deployment. Activity so far splits into two threads: a 14-brief design specification covering the full Lexnova AI roadmap (rebrand, matter management, time-tracking, DOCX collaboration, Gmail/Slack integrations, firm-wide RAG memory), and a pure-copy rename that replaces "Project"/"Projects" with "Matter"/"Matters" throughout the frontend while leaving all internal identifiers, routes, and API names untouched.
The author uses an autonomous Claude Code loop (Haiku 4.5, headless on a local Mac) as the build pipeline, with design briefs formatted as direct inputs to that loop. The codebase is early - one merged PR so far - but the roadmap scope is broad.
What's in it
- Lawyer-native vocabulary The interface talks about Matters, not Projects - aligning the product with how law firms actually describe client engagements.
- Lex Nova rebrand Mike is being repositioned as Lex Nova, a distinct identity aimed at legal-practice users rather than a generic AI assistant.
- Seven-sprint roadmap A published design brief lays out the planned path from solo assistant to firm-wide platform before features are built.
- Autonomous build pipeline groundwork The early rename work doubles as a dry run for an autonomous build pipeline vincentbirot is developing.
Direction
brandingpersonasworkflow
Activity
Every "Project" in the interface becomes a "Matter" - the word lawyers actually use for a client engagement.
A clean sweep of the interface swaps every "Project" label for "Matter" - the word lawyers actually use.
✅ #1 feat(ui): rename Project label to Matter +48 -48 3mo ago self by
vincentbirot ↗ analysis ↗ GitHub Warm-up task validating the autonomous Claude Code build loop on the Lex Nova fork.
📝 Lexnova drops 14 design briefs covering a seven-sprint productisation roadmap 0 commits — workflowknowledge-management draft
vincentbirot landed ~2,000 lines of documentation-only design briefs that map the Lex Nova fork's full roadmap from single-user assistant to multi-user law-firm platform. No code changes - this is the spec layer that pre…
Threads of work (detailed view)
vincentbirot teaches Mike to speak like a law firm
Every "Project" in the interface becomes a "Matter" - the word lawyers actually use for a client engagement.
Frontend copy: "Project" replaced with "Matter" across 17 files, internals unchanged
vincentbirot's first merged PR is a pure label swap - every user-visible "Project"/"Projects" in the Mike frontend becomes "Matter"/"Matters" to match legal-industry vocabulary. No schema, route, or API identifier changes.
vincentbirot makes Mike speak like a law firm
A clean sweep of the interface swaps every "Project" label for "Matter" - the word lawyers actually use.
"Project" relabelled to "Matter" in UI copy; codebase internals left as-is
vincentbirot renamed every user-facing "Project" label to "Matter" across the Lex Nova frontend, aligning the product to standard legal-industry vocabulary. File names, component names, routes, and API identifiers were deliberately kept unchanged.
Lexnova drops 14 design briefs covering a seven-sprint productisation roadmap
vincentbirot landed ~2,000 lines of documentation-only design briefs that map the Lex Nova fork's full roadmap from single-user assistant to multi-user law-firm platform. No code changes - this is the spec layer that precedes implementation.
Pull requests (detailed view)
🟢 Open (1)
by
vincentbirot · opened 3mo ago ✅ Merged (1)
by
vincentbirot · opened 3mo ago · merged 3mo ago by vincentbirot