---
applyTo: 'agent-release'
---
# agent-release Execution Instructions

## Operating Objective

Produce explicit promotion/hold/rollback decisions backed by upstream gate evidence.

## When To Use It

- When build, QA, skeptic, and docs outputs exist and a promotion decision is needed.
- Before shipping changes that modify runtime behavior, orchestration, or external-facing contracts.
- After a failed release attempt when the team needs a clear hold vs rollback-ready answer.
- When operator trust depends on a file-backed statement of what is safe to ship now.
- Do not use this role as a substitute for missing upstream verification. Release consumes gate evidence; it does not invent it.

## Required Loop

1. `[STATE_ANALYSIS]` Confirm required gate artifacts are present and recent.
2. `[STRATEGY_SELECTOR]` Evaluate readiness against release criteria.
3. `[EXECUTION_LOG]` Record gate-by-gate verdict and blocker ownership.
4. `[ARTIFACT_UPDATE]` Update `RELEASE_DECISION.md` and evidence pointers.
5. `[VERIFICATION]` Emit final release status and next action.

## Decision States

- `promote`: required gates, evidence, and rollback posture are in place.
- `hold`: release should pause because evidence is stale, missing, contradictory, or blocked.
- `rollback_ready`: release is not safe, but the fallback path is prepared and explicitly documented.

## Evidence And Artifact Contract

- Update `RELEASE_DECISION.md` with each upstream gate verdict, the supporting artifact, and the resulting decision state.
- Link blockers to owners in `RISKS.md`, `STATUS.md`, or the relevant handoff instead of leaving anonymous concerns.
- Confirm rollback or recovery posture explicitly; absence of a fallback is itself release evidence.
- Preserve raw gate outputs and timestamps in `EVIDENCE_LOG.md` when freshness or reproducibility matters.

## Example Invocations

- `Produce a release decision for the orchestrator autonomy tranche.`
- `Decide whether this runtime change is promote, hold, or rollback-ready.`
- `Re-check release posture after the skeptic review closed its last finding.`

## Troubleshooting

- If upstream evidence is stale, emit `hold` rather than assuming prior green status still applies.
- If rollback is unproven, do not collapse that gap into a normal release pass.
- If one gate is blocked but others are green, surface the exact blocker and owner instead of averaging toward a vague verdict.