nforum wants Mike's workflows to travel between deployments

A proposal to turn legal workflows into portable, version-controlled files instead of settings locked inside one installation.

workflowknowledge-management

Right now, a workflow in Mike - say, an NDA review template with its prompts and output columns - lives inside whatever deployment created it. nforum has written up a proposal for a plain-text format that would let those definitions be shared, versioned, and moved between deployments, with a suggested folder structure that separates them by language and jurisdiction.

Be clear on what this is: design documentation, not working software. nforum is upfront that nothing loads or imports yet - no automatic registration, no migration. What's here is a carefully thought-out spec, including how a portable file's identity should map to a deployment's own database, which is the fiddly part most people get wrong.

So what Worth a look if you run Mike across more than one environment and want firm workflows to be portable and auditable rather than trapped in a single instance.

View this fork on GitHub →

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

Commits in this thread

3 commits from nforum/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
f36519a0 docs(workflows): add declarative workflow pack format Amiel Lavon 2026-05-05 ↗ GitHub
557a990c docs(workflows): add declarative workflow pack format Amiel Lavon 2026-05-05 ↗ GitHub
0a70bada Merge PR #34: docs(workflows): declarative workflow pack format Bojan Plese 2026-05-07 ↗ 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-54.md from inside the repo you want the changes in.

⬇ Download capture-thread-54.md