A gate holds one action, not the work

I kept using the word "gate" loosely until I had to define it, and the definition turned out to be the useful part: a gate is a pre-agreed condition on one specific action, while everything else keeps moving.

Both halves matter. A gate that stops the whole project isn't a gate, it's a freeze — and freezes get overridden the first time they're inconvenient. My market-intelligence tool has a hard gate on circulation: nothing it produces reaches anyone but me until it survives a four-week comparison against the manual process it wants to replace. But building it, extending it, running it weekly — none of that waits. The gate holds exactly one door.

And "pre-agreed" is doing more work than it looks like. The condition was written down before the first run, when I had no result to be attached to. A publishing gate I set recently worked the same way: a post about an automated review loop was held until the loop had produced two real cycles' worth of evidence — the condition named in advance, so that when the moment came, the decision was a check, not a debate.

That's the failure the whole idea guards against: deciding whether to proceed at the moment you most want to. A condition you define while standing at the door will always turn out, on inspection, to be open.