open-legal-products puts Mike's workflow catalogue under database control

Mike is making its built-in and add-on legal workflows easier to manage as a live product, rather than a set of files shipped with the software.

workflowinfrastructure

The maintainers have moved the workflow catalogue into the database, including the default experiences and optional add-ons. That creates one source of truth for the workflows that shape how users interact with Mike.

  • A dedicated release step imports and validates the catalogue before the service starts.
  • Reference materials can be stored alongside workflow records in compatible cloud storage.
  • User defaults, quick actions, chat, and add-ons now draw from the same catalogue.
  • Releases can pin the workflow source to a specific GitHub version for repeatable deployments.

The change also adds checks and limits around downloaded workflow material, helping make catalogue updates more controlled.

So what Legal teams and product owners should care if they need dependable workflow updates across deployments without treating every change as a code release.

View this fork on GitHub →

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

Commits in this thread

2 commits from open-legal-products/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
1d92cbad refactor(workflows): ingest Mike catalog into database willchen96 2026-08-23 ↗ GitHub
a4126eab Merge pull request #376 from open-legal-products/codex/workflow-catalog-db Will Chen 2026-08-23 ↗ GitHub
Unify Mike workflows in the database

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

⬇ Download capture-thread-1264.md