| name | gds-rollout-policy |
| description | Use this skill only when the owner explicitly asks to roll out an immutable GDS bundle or policy version across managed repositories. Plan canaries and bounded waves, apply approved repository changes, pause on failures, and verify adoption. Do not use it to edit canonical policy or publish a bundle. |
| disable-model-invocation | true |
Contract
Roll out one verified immutable bundle through canaries and bounded waves.
Use when
- A released bundle must be adopted by selected managed repositories.
Do not use when
- The bundle is not released, trusted, or verified.
- The request is to author policy or release the control plane.
Inputs
- Exact source and target bundle identities and digests.
- Target selector, rollout rings, gates, and approval.
Preconditions
- Verify artifact identity, digest, attestation, release sequence, and rollback
target.
- Run
gds rollout plan --file <rollout-request> and present exact target
repositories and writes.
- Obtain approval for the concrete rollout plan.
Workflow
- Apply canary subplans.
- Verify projections, harness discovery, required checks, and security gates.
- Advance one bounded wave only when all gates pass.
- Pause immediately on security or threshold failure.
- Reconcile final adoption state.
Stop conditions
Stop on stale plan, changed target state, trust failure, missing rollback,
unexpected generated diff, wave failure, or revoked approval.
Verification
gds rollout plans only and has no apply or verify mode. After each wave and at
completion, verify each target with its own operation-specific verify command,
then re-run gds rollout plan --file <rollout-request> --json to reconcile
remaining adoption.
Output
Return per-wave results, adoption counts, paused targets, evidence, and exact
rollback or continuation state.
References
No additional runtime reference is required; the rollout plan carries its gates
and rollback.
