amal66 makes legal workflow packs portable

Teams can now move reusable legal workflows between Mike environments, with clearer rules for what a valid pack contains.

workflowsecurity

amal66 has added export and import support for workflow packs: reusable sets of instructions that shape how work moves through the system. The accompanying format documentation gives teams a common structure for sharing and checking those packs.

That is useful for firms and legal-product teams building a library of repeatable matter workflows. But portability also widens the trust boundary: an imported pack should be reviewed like any outside-supplied operational content, rather than treated as automatically safe.

So what Legal-ops leaders standardising workflows across teams should care because reuse becomes easier, but governance around imported instructions matters just as much.

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

SHA	Subject	Author	Date
`4378b6af`	feat(chapter-31): make workflows exportable and importable	Amal	2026-05-24	↗ GitHub
commit body Chapter: 31 - Workflow portability. Plain-English map: Add endpoints for exporting and importing workflows as `.mikeworkflow.json` files. Why it matters: Workflows capture reusable legal know-how. Users should be able to move them between Mike instances, teams, and environments without database access. Principle: Useful knowledge should be portable. Precedent borrowed: Upstream PR #59. Upstream base: willchen96/mike@d39f580. Original local commit: 212fbbe.
`c32e9307`	docs(chapter-32): define the workflow pack format	Amal	2026-05-24	↗ GitHub
commit body Chapter: 32 - Shared workflow contract. Plain-English map: Add a JSON Schema and human documentation for workflow packs, including examples and field explanations. Why it matters: Portable files need a shared contract. A schema lets editors, importers, and forks validate workflow packs in the same way. Principle: Schema-first formats reduce fragmentation. Precedent borrowed: Upstream PR #34 and workflow-heavy jurisdiction and practice-area forks from the fork report. Upstream base: willchen96/mike@d39f580. Original local commit: 557e647.

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

⬇ Download capture-thread-2012.md