Approval gate — Modern Auditing

A required, recorded human decision that stands between machine-performed work and the audit record.

An approval gate is what turns automation into assurance. Without one, an agent’s output is an assertion nobody signed; with one, it is a proposal a named person accepted, on a date, with the evidence attached.

Three properties make a gate real rather than decorative:

It blocks. The work does not enter the record until approval happens. A notification that something already occurred is a log entry, not a gate.
It is attributable. A specific human, not a shared account or a role, is recorded as the approver.
It carries context. The approver can see what the agent did and what it relied on, in enough detail to disagree. An approval given without the ability to disagree is a formality.

Gates are also where most implementations quietly fail. Under time pressure teams widen the scope of what auto-approves, and within a couple of cycles the gate has become an audit trail of clicks. The countermeasure is to measure it: if approval time per item falls toward zero and rejection rate is flat at nought, nobody is reading.