Declarative workflow pack format proposed (docs and schema only)
nforum's amiel-35 proposes a YAML-based workflow pack format checked into the repo, with a JSON Schema and two example files. No importer exists yet - this is a design artifact for a future build.
The two commits add docs/workflows.md (162 lines), schemas/workflow.schema.json, and two example packs (simple-assistant.workflow.yaml, simple-tabular-review.workflow.yaml). No code changes. The proposed fields map directly to the current workflow DB columns: id, title, type (assistant or tabular), practice, jurisdiction, language, version, is_system, prompt_md, and columns_config. Required fields are id, title, type, and prompt_md; tabular workflows additionally require columns_config with at least one column including name, format, and prompt.
The id field is explicitly a stable file-level identifier, not a database PK. A follow-up commit clarifies this in the docs and adds a description to the schema: a future importer can use the pack id directly or derive a deterministic UUID from it when the DB requires UUID primary keys.
The suggested directory layout is workflow-packs/<language>/<jurisdiction>/<practice>/<id>.workflow.yaml, with schemas/ and docs/ at the repo root. Nothing about this proposal changes runtime behavior or the existing DB schema.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?