Most release checklists are theater: a wiki page of items everyone affirms under deadline pressure. The information needed for a real go/no-go — open regressions, unfinished migrations, flag states, support load — is scattered across systems, and assembling it honestly takes longer than anyone has on release day.
So the decision quietly degrades into “CI is green, ship it,” and the items the checklist existed to catch surface in production.
A Fleet workflow assembles the release readiness report from your actual sources, an independent review step hunts for risks the draft underplays, and the release owner makes the go/no-go call at an approval gate — with the run literally paused until they decide.
| Step | Kind | What it does |
|---|---|---|
readiness |
Document | “Assemble the release readiness report: open issues, migration state, rollback plan, known risks.” Reads docs/runbooks/*.md, docs/releases/*.md, migrations/**. |
risk-review |
Review | “Adversarially review the readiness report. Flag understated risks and missing rollback steps.” |
go-no-go |
Approval gate | Pauses the run for a human sign-off; records the approver, timestamp, and note. |
announce |
Notify | Delivers the result to the named recipients. |
You build this once on the dashboard canvas; your self-hosted Fleet worker pulls the definition and runs it against your repository.
The approver sees the readiness document and the risk reviewer's flags side by side. “Go” is a recorded decision with a name and timestamp attached to the exact report that justified it. “No-go” stops the run and the record says why.
Readiness report → adversarial risk review → human go/no-go gate → announce. The gate is the point: the release decision becomes an auditable artifact instead of a Slack message.
Teams with a formal release owner role, regulated environments where ship decisions need evidence, and anyone who has discovered after an incident that nobody remembers who decided to ship.
No — it sits above them. CI answers 'does it build and pass tests.' The gate answers 'should we ship': migrations, rollback readiness, open regressions, support capacity. CI green is one input to the readiness report, not the decision.
The recipients named on the approval step. They get an email deep-linking to the decision page, and the recorded decision carries the approver's identity.
One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.
