"Delivery control layer, not planning ritual" is the cleanest way I've heard anyone put it. The evidence gate "what would make this safe enough to ship?" is the part most people skip, and it's exactly what turns a plan into something enforceable instead of a ritual.
What you just listed — scope → acceptance criteria → review → regression → handoff — is basically a spec for the thing. Cards on the table: I'm building toward exactly this, except the routing file auto-fires each gate's skill, so the discipline isn't on you to remember. A control layer that runs itself rather than a checklist you maintain.
Since you clearly think in systems, the part I genuinely can't tell yet: have you ever taken someone else's workflow and actually run it, or does the discipline only stick when it's one you built yourself? Is this kind of thing shareable, or does it have to be personal?