nforum sketches a file format for legal workflows

Amiel Lavon's contribution to nforum's fork doesn't change a single line of working code. It's a written proposal - a schema and two worked examples - for what a "workflow pack" should look like on disk: a small YAML file describing a workflow's title, type, practice area, jurisdiction, language, version, and the prompt text that drives it.

The point is governance. Today, the prompts and column configurations that shape how Mike reviews a contract or runs an intake live inside the database, edited through the app. Treating them as files means they can be reviewed in pull requests, diffed across versions, and shipped between firms or teams the same way code is. A second commit clarifies that the file's identifier is stable and independent of any database key, so the same pack can move between installations cleanly. The actual importer is deferred - this is laying down the standard before anyone writes against it.