Release Readiness

status="ready" · five workstreams, 74 checks. Two rows are blocked, two are waiting and one is clear, so the card leads with 14 open items — 5 known bad, 9 simply not in yet — and derives No-go from them: 3 checks failed, 1 critical blocker open and 1 signature refused. The mix reads 89% / 4% / 7%, which adds to exactly 100 because whole per cents are apportioned by largest remainder. Click a row to pin it to the readout.

Release readiness · v4.12

Release train 27 · sign-off board

14

open items

5 failing and 9 waiting

No-go

3 checks failed, 1 critical blocker open and 1 signature refused

5 workstreams · 66 of 74 checks passed · 2 of 5 signatures in · sign-off closes Mon, Mar 30, 3 days left

66 passed89%3 failed4%5 waiting7%

Go requires every check to have reported a pass, no open blocker and every signature in. One failed check, one critical blocker or one refused signature makes the release no-go on its own; anything merely outstanding holds it. The verdict is computed from the rows above every render — it is never carried in the payload, so it cannot drift away from the evidence printed under it. Mix per cents are apportioned by largest remainder so the three add to exactly 100, and a slice holding at least one check never prints 0%.

Click a workstream to pin it to the readout; with one focused, ↑ and ↓ walk the list and Home / End jump to the ends.

Release readiness · v4.12. Verdict: No-go — 3 checks failed, 1 critical blocker open and 1 signature refused. 5 workstreams: 1 cleared, 2 waiting, 2 blocked. Checks: 66 passed (89%), 3 failed (4%), 5 waiting (7%). 3 open blockers, 1 of them critical. 2 of 5 signatures in. Sign-off closes Mon, Mar 30, 3 days left. The verdict rests on Payments API. Go requires every check to have reported a pass, no open blocker and every signature in; a failed check, a critical blocker or a refused signature is a no-go on its own, and anything merely outstanding holds the release. Every workstream is listed in the table below.

Every workstream in this release with its check counts, its sign-off, its open blockers, the state derived from them and what is standing in the way.
Workstream	Passed	Failed	Waiting	Sign-off	Open blockers	State	In the way
Payments API	18	2	1	Sign-off pending with Doyle Osinski, Payments lead	Refunds double-charge when the gateway retries (critical); Idempotency keys expire after 60s (major)	Blocked	2 checks failed, 1 critical blocker open, 1 check still waiting, 1 blocker open and sign-off pending with Doyle Osinski
Mobile app	15	1	0	Sign-off refused by Sigurd Willms, Mobile QA — Crash-free sessions at 99.6%, under the 99.8% gate	none	Blocked	1 check failed and sign-off refused by Sigurd Willms
Web checkout	24	0	4	Signed by Priya Raman, Web lead	Apple Pay button misaligned on iPad (minor)	Waiting	4 checks still waiting and 1 blocker open
Docs & release notes	0	0	0	Sign-off has no owner	none	Waiting	Sign-off has no owner
Search relevance	9	0	0	Signed by Tomas Weller, Search lead	none	Cleared	nothing outstanding

status="empty" · a valid payload with no workstreams. It renders the zero state, never a Go: nothing assessed is not the same as nothing wrong, and a green light on an empty board is the most dangerous thing this card could print.

Release readiness · v4.12

Release train 27 · sign-off board

No workstream has been assessed

A go/no-go verdict is only as real as the rows under it. Add the workstreams this release ships — their checks, their sign-off owner and their open blockers — and the call is computed from them.

status="loading" · a silhouette of the ready layout — hero numeral, verdict pill, mix bar, four rows — so nothing jumps when the data lands. It is aria-hidden beside an sr-only role=status, and no timer is involved.

Release readiness · v4.12

Release train 27 · sign-off board

status="error" · the gate API failed. Try again appears only when onRetry is passed, and pressing it switches to ready. No verdict is shown at all — a go/no-go call on a board that could not be read would be a guess wearing the clothes of a decision.

Release readiness · v4.12

Release train 27 · sign-off board

Couldn’t load release readiness

The release gate API returned 503 after three attempts.

No verdict is shown: a go/no-go call on a board that could not be read would be a guess wearing the clothes of a decision.

Go. All 83 checks passed, no blocker is open and all four signatures are in, so the open item count reaches 0 and only then does the verdict turn green — the big number and the verdict are the same fact printed twice. Sign-off closes the same day, so the countdown reads today rather than a day count.

Release readiness · v4.11

Release train 26 · signed off

0

open items

nothing is standing in the way

Go

Every check passed, no blocker is open, every signature is in

4 workstreams · 83 of 83 checks passed · 4 of 4 signatures in · sign-off closes today, Tue, Feb 17

83 passed100%0 failed0%0 waiting0%

Go requires every check to have reported a pass, no open blocker and every signature in. One failed check, one critical blocker or one refused signature makes the release no-go on its own; anything merely outstanding holds it. The verdict is computed from the rows above every render — it is never carried in the payload, so it cannot drift away from the evidence printed under it. Mix per cents are apportioned by largest remainder so the three add to exactly 100, and a slice holding at least one check never prints 0%.

Click a workstream to pin it to the readout; with one focused, ↑ and ↓ walk the list and Home / End jump to the ends.

Release readiness · v4.11. Verdict: Go — every check passed, no blocker is open, every signature is in. 4 workstreams: 4 cleared, 0 waiting, 0 blocked. Checks: 83 passed (100%), 0 failed (0%), 0 waiting (0%). 0 open blockers, 0 of them critical. 4 of 4 signatures in. Sign-off closes today, Tue, Feb 17. The verdict rests on Payments API. Go requires every check to have reported a pass, no open blocker and every signature in; a failed check, a critical blocker or a refused signature is a no-go on its own, and anything merely outstanding holds the release. Every workstream is listed in the table below.

Every workstream in this release with its check counts, its sign-off, its open blockers, the state derived from them and what is standing in the way.
Workstream	Passed	Sign-off	Open blockers	State	In the way
Payments API	22	Signed by Megane King, Payments lead	none	Cleared	nothing outstanding
Web checkout	31	Signed by Abigail Green, Web lead	none	Cleared	nothing outstanding
Mobile app	18	Signed by Madison Kreiger, Mobile QA	none	Cleared	nothing outstanding
Search relevance	12	Signed by Victoria Altenwerth, Search lead	none	Cleared	nothing outstanding

Hold, not No-go. Nothing has failed and nothing is refused: 5 checks are still running, 1 minor blocker is open and 1 signature is outstanding — 7 open items, all of them merely unknown. The cutoff spans the night European clocks go forward, so the gap is 4 calendar days but under 3.96 × 24 hours; the card says 4 days left because it counts civil days in the release team's zone instead of dividing milliseconds.

Release readiness · v4.13

Release train 28 · waiting on evidence

7

open items

7 waiting

Hold

5 checks still waiting, 1 blocker open and 1 signature outstanding

3 workstreams · 60 of 65 checks passed · 2 of 3 signatures in · sign-off closes Tue, Mar 31, 4 days left

60 passed92%0 failed0%5 waiting8%

Go requires every check to have reported a pass, no open blocker and every signature in. One failed check, one critical blocker or one refused signature makes the release no-go on its own; anything merely outstanding holds it. The verdict is computed from the rows above every render — it is never carried in the payload, so it cannot drift away from the evidence printed under it. Mix per cents are apportioned by largest remainder so the three add to exactly 100, and a slice holding at least one check never prints 0%.

Click a workstream to pin it to the readout; with one focused, ↑ and ↓ walk the list and Home / End jump to the ends.

Release readiness · v4.13. Verdict: Hold — 5 checks still waiting, 1 blocker open and 1 signature outstanding. 3 workstreams: 0 cleared, 3 waiting, 0 blocked. Checks: 60 passed (92%), 0 failed (0%), 5 waiting (8%). 1 open blocker, 0 of them critical. 2 of 3 signatures in. Sign-off closes Tue, Mar 31, 4 days left. The verdict rests on Payments API. Go requires every check to have reported a pass, no open blocker and every signature in; a failed check, a critical blocker or a refused signature is a no-go on its own, and anything merely outstanding holds the release. Every workstream is listed in the table below.

Every workstream in this release with its check counts, its sign-off, its open blockers, the state derived from them and what is standing in the way.
Workstream	Passed	Waiting	Sign-off	Open blockers	State	In the way
Payments API	20	3	Signed by Ingrid Sollberger, Payments lead	none	Waiting	3 checks still waiting
Mobile app	14	2	Signed by Rui Marques, Mobile QA	Onboarding copy untranslated in pt-BR (minor)	Waiting	2 checks still waiting and 1 blocker open
Web checkout	26	0	Sign-off pending with Guy Block, Web lead	none	Waiting	Sign-off pending with Guy Block

One failed check among 481. Its exact share is 0.21%, which floors to zero — so the apportionment gives a non-empty slice a 1% floor and takes the point off the largest slice: the legend reads 99% / 1% / 0% and still adds to 100. The red segment also carries a minimum width, so a single failure never disappears into the rail. One open item, singular, and still No-go.

Release readiness · v4.14-rc1

Nightly gate · one failure in 481 checks

1

open item

1 failing

No-go

1 check failed

2 workstreams · 480 of 481 checks passed · 2 of 2 signatures in · sign-off closes Thu, Apr 9, 1 day left

480 passed99%1 failed1%0 waiting0%

Go requires every check to have reported a pass, no open blocker and every signature in. One failed check, one critical blocker or one refused signature makes the release no-go on its own; anything merely outstanding holds it. The verdict is computed from the rows above every render — it is never carried in the payload, so it cannot drift away from the evidence printed under it. Mix per cents are apportioned by largest remainder so the three add to exactly 100, and a slice holding at least one check never prints 0%.

Click a workstream to pin it to the readout; with one focused, ↑ and ↓ walk the list and Home / End jump to the ends.

Release readiness · v4.14-rc1. Verdict: No-go — 1 check failed. 2 workstreams: 1 cleared, 0 waiting, 1 blocked. Checks: 480 passed (99%), 1 failed (1%), 0 waiting (0%). 0 open blockers, 0 of them critical. 2 of 2 signatures in. Sign-off closes Thu, Apr 9, 1 day left. The verdict rests on Platform regression suite. Go requires every check to have reported a pass, no open blocker and every signature in; a failed check, a critical blocker or a refused signature is a no-go on its own, and anything merely outstanding holds the release. Every workstream is listed in the table below.

Every workstream in this release with its check counts, its sign-off, its open blockers, the state derived from them and what is standing in the way.
Workstream	Passed	Failed	Waiting	Sign-off	Open blockers	State	In the way
Platform regression suite	398	1	0	Signed by Mable Welch, Platform lead	none	Blocked	1 check failed
Consumer contract tests	82	0	0	Signed by Hélène Dupont, API lead	none	Cleared	nothing outstanding

heroMetric="pass-rate" on a workstream with no automated gate at all. There is no denominator, so the hero prints an em dash rather than inventing 0% or 100%, the mix bar says no check reported, and the footnote states outright that this verdict rests on a signature alone.

Release readiness · legal review

Manual gate · no automated checks

—

no checks reported

this verdict rests on blockers and signatures alone

Hold

1 signature outstanding

1 workstream · no checks reported · 0 of 1 signature in

No automated check reported on this release

Go requires every check to have reported a pass, no open blocker and every signature in. One failed check, one critical blocker or one refused signature makes the release no-go on its own; anything merely outstanding holds it. The verdict is computed from the rows above every render — it is never carried in the payload, so it cannot drift away from the evidence printed under it. Not one check was reported, so this verdict rests on blockers and signatures alone.

Click a workstream to pin it to the readout; with one focused, ↑ and ↓ walk the list and Home / End jump to the ends.

Release readiness · legal review. Verdict: Hold — 1 signature outstanding. 1 workstream: 0 cleared, 1 waiting, 0 blocked. Checks: no checks were reported. 0 open blockers, 0 of them critical. 0 of 1 signature in. The verdict rests on Legal & privacy review. Go requires every check to have reported a pass, no open blocker and every signature in; a failed check, a critical blocker or a refused signature is a no-go on its own, and anything merely outstanding holds the release. Every workstream is listed in the table below.

Every workstream in this release with its check counts, its sign-off, its open blockers, the state derived from them and what is standing in the way.
Workstream	Passed	Failed	Waiting	Sign-off	Open blockers	State	In the way
Legal & privacy review	0	0	0	Sign-off pending with Vicky Quigley, Counsel — Waiting on the updated sub-processor list	none	Waiting	Sign-off pending with Vicky Quigley

order="given" with heroMetric="cleared" · eight release-train stages in the payload's own run order, three of them cleared, even though three others are blocked. Names longer than the row are clipped by the browser rather than wrapping the row into a paragraph. The cutoff instant falls on the next day in Tokyo, so the date and the countdown both come from the same value read in that zone.

Release readiness · v5.0

Release train 31 · stages in run order

3

of 8 workstreams cleared

3 blocked and 2 waiting

No-go

3 checks failed, 1 critical blocker open and 1 signature refused

8 workstreams · 143 of 155 checks passed · 4 of 8 signatures in · sign-off closes Fri, May 15, 4 days left

143 passed92%3 failed2%9 waiting6%

Go requires every check to have reported a pass, no open blocker and every signature in. One failed check, one critical blocker or one refused signature makes the release no-go on its own; anything merely outstanding holds it. The verdict is computed from the rows above every render — it is never carried in the payload, so it cannot drift away from the evidence printed under it. Mix per cents are apportioned by largest remainder so the three add to exactly 100, and a slice holding at least one check never prints 0%.

Click a workstream to pin it to the readout; with one focused, ↑ and ↓ walk the list and Home / End jump to the ends.

Release readiness · v5.0. Verdict: No-go — 3 checks failed, 1 critical blocker open and 1 signature refused. 8 workstreams: 3 cleared, 2 waiting, 3 blocked. Checks: 143 passed (92%), 3 failed (2%), 9 waiting (6%). 3 open blockers, 1 of them critical. 4 of 8 signatures in. Sign-off closes Fri, May 15, 4 days left. The verdict rests on iOS 26 compatibility sweep. Go requires every check to have reported a pass, no open blocker and every signature in; a failed check, a critical blocker or a refused signature is a no-go on its own, and anything merely outstanding holds the release. Every workstream is listed in the table below.

Every workstream in this release with its check counts, its sign-off, its open blockers, the state derived from them and what is standing in the way.
Workstream	Passed	Failed	Waiting	Sign-off	Open blockers	State	In the way
Identity & access management platform	34	0	0	Signed by Marlon Cole, Security	none	Cleared	nothing outstanding
Billing, invoicing and dunning	28	1	0	Sign-off pending with Samantha Hane, Revenue lead	Dunning emails retry without backoff (major)	Blocked	1 check failed, 1 blocker open and sign-off pending with Samantha Hane
Merchant onboarding — KYC vendor cutover	12	0	6	Sign-off pending with Yolanda Schmidt, Risk	none	Waiting	6 checks still waiting and sign-off pending with Yolanda Schmidt
Notifications fan-out	19	0	0	Signed by Sara Nyberg, Platform lead	none	Cleared	nothing outstanding
Data warehouse backfill and schema migration v7	7	0	2	Sign-off has no owner	Backfill deadlocks the events table at 40M rows (critical)	Blocked	1 critical blocker open, 2 checks still waiting and sign-off has no owner
Partner API v3 deprecation shims	22	0	0	Signed by Loyal Jakubowski MD, API lead	Deprecation header missing on 2 routes (minor)	Waiting	1 blocker open
iOS 26 compatibility sweep	16	2	1	Sign-off refused by Rosamond Welch DVM, Mobile QA — Two regressions in the share flow	none	Blocked	2 checks failed, sign-off refused by Rosamond Welch DVM and 1 check still waiting
Status page and incident comms	5	0	0	Signed by Marek Duda, SRE	none	Cleared	nothing outstanding

Contract refusal: the feed replays one workstream under an id that is already on the board. Every number here is a sum over ids, so the repeat would be counted twice and the verdict would rest on a workstream that does not exist — the contract refuses and the component renders the reason instead of a plausible lie.

Release readiness · v4.12

Feed replays one workstream under the same id

This board can’t be rolled up

Two workstreams share the id "payments". Every count in this card is a sum over ids, so the repeat would be added twice and the verdict would rest on a workstream that does not exist.

No verdict is shown: a go/no-go call on a board that could not be read would be a guess wearing the clothes of a decision.