amal66 gives Mike's backend a clearer legal-work spine

A behind-the-scenes restructure aims to make future changes safer without changing how Mike behaves today.

infrastructureworkflow

amal66 is breaking up Mike's oversized backend areas into smaller domain-focused units. Documents, projects, users, tabular review, chat, workflows and the library each get clearer boundaries between the web-facing layer and the work that handles legal data and business rules.

The practical payoff is less about a new button today than about safer change tomorrow. The same core for tabular extraction can now be used by both the live product and background workers, while testing can focus on the underlying work without recreating a full web session. The fork reports that existing endpoints and integration tests still behave as before.

This is the kind of unglamorous foundation that matters when a legal product needs to keep evolving without turning each improvement into a regression risk.

So what Legal-tech teams considering Mike should care if they value a codebase that is easier to review, test and extend as workflows grow.

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

SHA Subject Author Date

bfb2466e refactor(chapter-10): split routes into modules with validation and access guards Amal 2026-05-24 ↗ GitHub

SHA	Subject	Author	Date
`bfb2466e`	refactor(chapter-10): split routes into modules with validation and access guards	Amal	2026-05-24	↗ GitHub
commit body Chapter: 10 - API boundaries. Plain-English map: Introduce a module layer for API routes, validate incoming request shapes with Zod, and add authorization checks around tabular document access. Why it matters: Large route files make it hard to see where trust boundaries are. Validation and access checks need to sit at the boundary before data reaches deeper code. Principle: Validate inputs and authorize data access close to the edge of the system. Precedent borrowed: Upstream PR #155 and the fork report's strongest security signal: multiple forks independently patched CWE-639 style tabular-document access bugs. Upstream base: willchen96/mike@d39f580. Original local commit: f913869.

commit body

Chapter: 10 - API boundaries.

Plain-English map:
Introduce a module layer for API routes, validate incoming request shapes with
Zod, and add authorization checks around tabular document access.

Why it matters:
Large route files make it hard to see where trust boundaries are. Validation
and access checks need to sit at the boundary before data reaches deeper code.

Principle:
Validate inputs and authorize data access close to the edge of the system.

Precedent borrowed:
Upstream PR #155 and the fork report's strongest security signal: multiple
forks independently patched CWE-639 style tabular-document access bugs.

Upstream base: willchen96/mike@d39f580.
Original local commit: f913869.

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

⬇ Download capture-thread-1383.md