open-legal-products puts Mike's workflow library under one roof
Mike's built-in workflows, add-ons and shortcuts now come from a single versioned catalog instead of generated files scattered through the product.
The move makes the workflow library more governable: the team can update it through a deliberate release step, then run the application against the approved catalog without fetching or rebuilding it at startup.
- Built-in and add-on workflows now share one database-backed catalog.
- User-editable defaults and Quick Actions draw from that same source.
- Compatibility checks and chat lookups use the unified records.
- Release imports pin the source to a specific version, validate its contents and activate workflows and reference material together.
- The import is designed to be safely repeatable, while temporary download material is cleaned up.
That is less about a flashy new feature than operational confidence: a legal team can know which workflow set is live, and update it deliberately rather than letting application startup change it.
So what Legal-ops leaders and product teams should care if they need reliable, auditable control over the workflows users see and run.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?