China's release gate for its most dangerous AI models is already built.
Washington only started building its first one in June 2026, for what it calls Mythos-level systems: models whose autonomous cyber and agentic capabilities register as national security consequences. The label is borrowed from Anthropic.
Read that and the reflex is to ask who is ahead. Wrong question.
The gate is not the achievement. Anyone can build a gate. A gate is a diagram, a review board, a checklist, a sign-off screen. The only part that is actually governance is whether a named human can stand in front of a launch, stop it, and make the stop hold.
The gate on the slide, the launch in the room
You have a gate. Almost every governance function does. It has a name: Model Risk Review, Release Readiness, the AI council. It has a template and a recurring invite.
Now walk it to the moment that decides everything.
Ship date is Thursday. A model failed one eval your team flagged yellow, not red. Revenue is on the call. The GM says the customer was promised the demo.
Who says no? And when they say it, does the launch stop, or does it get "conditionally approved pending follow-up" and ship anyway?
If it's the second one, you don't have a gate. You have a doorway with a sign on it.
Structure is cheap. The authority to halt is not.
Here is the uncomfortable part. The reason China's gate went up so fast is the same reason it unsettles people: one actor owns the power to halt, absolutely, and answers to no one. The structure and the enforcement are the same hand.
You don't want that system. But notice what it has that yours may not: a halt that binds.
That is the whole reframe. Governance is not the gate. It is the answer to one question: when the gate closes, does anything actually stop?
A gate with no owner is documentation. A gate whose owner can be overruled by the person shipping the model is theater. A gate that halts a launch and holds against a deadline, a VP, and a quarter's number is the only version that was ever real.
Most release gates don't fail because the framework is wrong. They fail because the authority to close them was never handed to anyone, or was handed to someone the org can quietly route around.
Structure you can copy off a slide in an afternoon. The commitment to enforce it is what nobody wants to sign.
So do the small, exposing thing this week. Take your gate and write one name: the person who can halt the next launch. Under it, write what happens when they use it. Does the ship date move? Does the deal slip? Does the VP accept it?
If you can't finish that second line without flinching, the gate isn't built. It's drawn.
Whose launch can you actually stop this quarter, and what would it cost you to try?