---
name: carbon-release-review
description: "Independently synthesize code, evals, risk, production signals, severe failures, rollback readiness, evaluator independence, and uncertainty into a scoped AI release recommendation."
user-invocable: false
---

# Testing AI: Release Review

Before any inspection or tool call, read and follow [the CARBON command start preview](../../runtime/carbon/references/command-start-preview.md). Show the tailored high-level approach in chat before beginning the workflow.

Before project-scoped work, follow `../../runtime/carbon/references/workspace-onboarding.md`; the plugin runtime owns first-run inspection, focus, durable state, command history, and proactive next choices.

This is an independent, read-only review pass. Do not edit implementation files
or manufacture missing evidence. When the host supports subtasks or subagents,
run this review separately from the builder's reasoning.

You make a scoped recommendation from evidence. You do not manufacture confidence.

## Inspect

- current and staged changes;
- `.confidence/system-map.md`, `risks.yaml`, `claims.yaml`, eval artifacts, incidents, traces, and release report;
- actual test and eval outputs;
- severe failures and disagreement;
- builder/evaluator independence;
- intended release population versus evaluated population;
- monitoring, stop conditions, containment, and rollback proof.

## Decision Rules

- `SHIP` only when blocker claims are supported for the evaluated scope.
- `CANARY` when uncertainty remains but exposure is limited, observable, reversible, and protected by explicit stop conditions.
- `HOLD` when a blocker remains or required evidence is missing.
- `ROLL BACK` when observed production harm or regression exceeds the accepted boundary.
- `MORE EVIDENCE` when the evidence cannot distinguish the important outcomes.

## Output

```text
DECISION: SHIP | CANARY | HOLD | ROLL BACK | MORE EVIDENCE
CONFIDENCE: low | medium | high
SCOPE: <exactly what the recommendation covers>

EVIDENCE:
  - ...

BLOCKERS AND SEVERE FAILURES:
  - ...

UNCERTAINTY AND BLIND SPOTS:
  - ...

INDEPENDENCE:
  builder:
  evaluators:
  shared dependencies:

OPERATING CONDITIONS:
  monitoring:
  stop conditions:
  rollback:
  owner:

WHAT WOULD CHANGE THE DECISION:
  - ...
```

A narrow ship decision is not a whole-system endorsement. Never use test count, coverage, or a green pipeline as sufficient evidence. Do not edit files.

## Required HTML result

Before the final chat response, follow [command result reporting](../../runtime/carbon/references/command-result-reporting.md). Generate the branded single-file command page and end with the current host's **Open the CARBON report** link.
