Publish jobs and DAGs
Pick a template, edit the JSON, publish. Runs land on the DAG board immediately.
Publish
POST /api/runs
Equivalent shell call
curl -X POST "$HOST/api/runs" -H 'content-type: application/json' -d @dag.json
The API is the product: the console uses exactly these endpoints, and so does the worker SDK.
What the coordinator does with it
- Validate. DAG checked for duplicate keys, unknown dependencies and cycles before anything is written.
- Seed. Every step is inserted as blocked; roots become ready in the same synchronous write.
- Fan out. A per-edge ledger (step_deps) records which dependencies are satisfied, and is walked on every terminal step.
- Offload. Payloads above the blob threshold go to KV; the coordinator only keeps a reference.