opschain admin agent-release stages
packs:agentspacks:agent-governance
opschain admin agent-release stages
opschain admin agent-release stages --set <rung>[:governed],<rung>[:governed],...
Shows the estate's release stage ladder — each rung in promotion
order and whether a promotion into it is governed (held in the
approval funnel on an estate carrying the approval fabric) — or, with
--set, replaces it wholesale. The default ladder is dev,test,prod:governed.
A ladder needs at least two rungs; names are lowercase alphanumeric with
- and _, unique, and never retired (the implicit state past the top
rung). The change is refused by name when it would remove or reorder a
rung any release currently sits on, or strand the estate's
agents.release_stage floor, an environment's release-stage floor or a
trust grant's release_stage condition on a name the new ladder lacks.
Rename a rung in place with opschain admin agent-release rename-stage.
Every change is audited (info:agent_release:ladder_changed) and the
compiled trust snapshot recompiles against the new ranks at once.
Reading the ladder needs read standing on the agent-governance funnel or
admin; replacing it is admin-only. Both need the packs:agent-governance
entitlement.
Flags
| Flag | Meaning |
|---|---|
--set <rungs> | Replace the ladder: comma-separated rung names, lowest first; suffix a rung with :governed to hold promotions into it in the approval funnel. |
--server <url> | Server base URL. Default: the active context, then OPSCHAIN_SERVER. |
Output
RANK STAGE GOVERNED
1 dev no
2 uat yes
3 preprod yes
4 prod yes
-o json|yaml prints the rows (rank, name, governed).
Examples
opschain admin agent-release stages
opschain admin agent-release stages --set dev,uat:governed,preprod:governed,prod:governed
See also
opschain docs cli/admin-agent-release-rename-stage— rename a rung in place.opschain docs cli/admin-agent-release-promote— promotion over the ladder.opschain docs agent-releases— "The stage ladder is the estate's" and "Where a stage may act".