Prototype · launch gate

One launch, every surface, one verdict.

The gate reads each public surface for a launch and returns go, at-risk or no-go — the same pass / warn / fail logic as my promotion QA engine, pointed at a launch board instead of a deal sheet. Pick a launch; switch on “Required before GA” to see which surfaces a readiness plan would have made mandatory.

Launches loaded5

Surfaces per launch6

Rule1 fail = no-go

Launch

Surface states are what the public pages showed on Sep 20, 2026; see the Findings page for URLs. “Required before GA” treats help center and an availability/migration statement as mandatory for any GA or deprecation, and N/A for early access.

Where it sits in the launch system

A launch board is supposed to be the single source of truth, with clear ownership of what must be true before GA. This gate is that list, made checkable: each surface gets an owner and a state, the launch can't be called GA while any required surface is red, and the same run on day 30 catches the article that never flipped from “Coming soon.”