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.
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.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?