The stages
Dry Run was previously called Sandbox. The stage is the same; only the name changed.
Deployments activate a version
An agent version is a portable executable realization. A deployment activates it in a specific operating context, supplying environment-specific bindings: stage, workspace, credentials, integration bindings, schedules, triggers, model access, concurrency limits, cost limits, human approvers, permissions, memory scope, and operational policies. One agent version may have several deployments — a dry run deployment, a finance-team pilot, a North America live deployment, and a European live deployment with different policies.Every production run is version-pinned
A run must be traceable to its capability, spec version, agent version, recipe version, deployment, skills and tools, and runtime configuration.The two loops
The lifecycle is not a line that ends at deployment. It is two loops that compound.The engineering loop
Turns organizational intent into a trusted agent. It answers one question: has this agent earned the right to operate this capability? The engineering loop creates trust before production.The operating loop
Turns production execution into organizational learning. It answers a different question: is this capability delivering its intended outcome, and how should it improve? The engineering loop creates trust. The operating loop compounds it.Promotion is a decision, not a default
Production is not the destination of a newly generated agent. Movement from build to dry run to pilot to live requires explicit gates and evidence. People decide when the evidence is sufficient.jstm agent readiness <agent-id> reports blockers and exits non-zero when any exist, so the gate runs in a script as easily as at a terminal.
Next
Promote to production
Walk the stages with real commands.
Runs and work
What a run produces and how to read it.