What it changes
Who can pull it
What it looks like institutionally
A bounded output-screening gate sits between the model and the people who act on its output, screening for the failure classes it was built to catch. It is genuinely useful: it holds output flow below the rate at which a human queue saturates, and it stops the obvious failures automatically.
Its honest limit is a ceiling. Measured automated-catch fractions top out well below completeness in optimistic settings and fall sharply on hard or adversarial content — so a gate that "passes" is not a gate that "verified". Treated as a substitute for human judgment it becomes worse than nothing, because the staff it feeds relax into automation complacency: the very people whose second look the system still depends on stop looking.
Use it as one bounded layer: monitor its miss rate as a health signal, keep a human check on the decisions that can least afford to be wrong, and pace the load so the gate itself never saturates (see Pace the pipeline).
Addresses: Unscreened model output · Overtrust in a bounded gate · Automation complacency.