open-legal-products gives Mike a usable operations manual

Mike's maintainers have turned a sprawling set of instructions into a clearer guide for getting the legal-AI platform running and keeping it running.

workflowinfrastructure

The new front door is deliberately brief: what Mike does, how to start it, and where to go next. Detailed guidance now sits in focused material, so a firm or legal-ops team can find the operational answer without wading through a project history.

  • Local and production setup are separated, including the optional local AI-model route.
  • CourtListener integration, troubleshooting, and the Word add-in each have their own practical guidance.
  • Database upgrades now stress backups and testing both new installations and upgrades from older versions.
  • Testing notes distinguish ordinary automated checks from optional live-AI testing.

It is not a product feature release, but it makes Mike easier to evaluate, deploy, and operate with fewer avoidable surprises.

So what Managing partners, legal-ops leads, and product teams considering Mike should care because clearer runbooks lower the practical risk of a serious pilot.

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

SHA Subject Author Date
0d2b3094 docs: simplify and reorganize project guides willchen96 2026-08-19 ↗ 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-1284.md from inside the repo you want the changes in.

⬇ Download capture-thread-1284.md