cargo-orchestration

# Cargo CLI — Orchestration Runtime operations for the Cargo platform. **What do you want to run?** ``` Need to run something? ├── Don't know the action yet → action list <keywords> ├── 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). > **Every node execution costs 0.01 credits — 1 credit per 100 — whatever the node is.** > `branch`, `filter`, `switch`, `variables` and the rest carry no provider price, but > they are not free: the charge is per *execution*, so a graph's cost has two terms, > `(provider cost × records) + (nodes × records ÷ 100)`. On step-heavy, action-light > graphs the second term dominates. It shows up in **no** per-node field...