cargo-orchestration

# Cargo CLI — Orchestration Runtime operations for the Cargo platform. **What do you want to run?** ``` Need to run something? ├── One action, one record → action execute ├── One action, many records → action execute-batch ├── Multiple actions chained │ ├── One-off / ad-hoc → run create --nodes (one record) │ │ batch create --nodes (many records) │ └── Reusable workflow → build a tool, then run create --workflow-uuid │ or batch create --workflow-uuid ├── Conversational AI agent → message create └── Testing ONE node of a workflow you're building → node execute (debug only — see below) ``` > **Fanning out across many records (`action execute-batch`, `batch create`)? Sample first.** Run 10–20 records, report the observed cost and hit-rate, then ask the user to approve the full enrollment — quoting the **record count** and the **credit estimate**. See [Create a batch → the sample gate](#the-sample-gate). > **`action execute`, not `node execute`, is the default for running something.** > `node execute` is a **debug** surface for a node that already lives in a workflow: > it requires `--workflow-uuid`, `--release-uuid`, `--node`, `--computed-config` > **and** `--context` (all five, enforced client-side), and it bills like any live > call. If you just want an operation's output — enrich a domain, call a connector > action, invoke a tool or agent — use `action execute` / `ac...