nwhitehouse writes the operations manual for Mike

The fork now ships with a 377-line README that doubles as the deployment playbook for a live legal-AI product.

infrastructureknowledge-management

Where the upstream project gives you three lines of README, nwhitehouse has replaced it with a working operations guide for the Olava deployment. It walks through the full production setup - the hosting stack, the database, the email infrastructure, the custom AI model with its quirks - plus all the environment variables and access rules that keep client data partitioned.

The most useful section is the gotchas: hard-won lore like the corporate email security tool that silently breaks Supabase confirmation links, or the Node version constraints that bite on deploy. There's also a candid backlog of deferred cleanups for whoever picks this up next. It reads less like documentation and more like a handoff note from someone who's been on call.

So what Anyone evaluating this fork - or thinking about productionising any open-source legal-AI tool - should read it before writing a line of code.

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

SHA Subject Author Date
9a360516 README: comprehensive handoff doc Nick Whitehouse 2026-05-02 ↗ GitHub
commit body
Replace the upstream's three-line README with a full operations and architecture guide for the Olava deploy: tech stack, repo layout, local dev path, the live Vercel + Railway + Supabase + Resend topology with all env vars, the email-domain whitelist + RLS story, the Olava-001 vLLM particulars (reasoning fields, custom tool-call format, fallback parser), known gotchas (Mimecast, Vercel verified commits, Nixpacks Node 18, CORS for the custom domain), and a backlog of deferred cleanups for the next person.

Co-Authored-By: Claude Opus 4.7 (1M context) <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-122.md from inside the repo you want the changes in.

⬇ Download capture-thread-122.md