Add server-side workflows with YAML files, task freeze and lead tools
This commit is contained in:
@@ -10,8 +10,6 @@
|
||||
|
||||
# M5 — Workflows
|
||||
|
||||
- Workflow definitions and storage
|
||||
A workflow is a sequence of stages, each with a role prompt template, a vendor and model, typed artifact inputs and outputs, an optional gate, and optional review profiles. Definitions, prompt templates and review profiles live on the server, not in repos, and export and import as files. A task freezes its workflow definition at intake, so later edits to the workflow don't change running tasks. No general DAG engine until a real workflow needs one.
|
||||
- Stages, gates and bounded loops
|
||||
Gates are human approval through the inbox, a review pass or an eval pass. Loops are bounded, for example `on_fail: { goto: build, max: 3, then: escalate }`.
|
||||
- Plan artifact
|
||||
|
||||
Reference in New Issue
Block a user