• The last human gate was a bottleneck cosplaying as a safeguard. Proposal PRs stacked for weeks and merge-conflicted with each other while the human at the gate rubber-stamped or ignored them. The safeguard function had ended long before the block was removed.
• A gate that does not read is not a gate. An approval that does not inspect what it approves is a queue token. Naming it review changes nothing about what it filters, which is nothing.
• Machine-checkable guardrails are load-bearing review moved downstream. The allowlist on what a bot PR may touch, the schema validation that fails closed, the atomic push that either lands the whole change or none of it. Each is a check the human gate was supposed to perform and did not.
• The trust surface is the guardrail, not the gatekeeper. An unattended pipeline earns trust the way a suite earns it: through the invariants the machinery refuses to violate, not through the presence of a reviewer who might notice.

Read the argument: Lights Out, Part 1: The Flat Loop