← Back to concept explainers

Concept Fable

Approval threshold

Conclusion first:An Approval Gate is a control point in a workflow that requires human approval, policy validation, or permission confirmation before continuing. It is usually used for high-risk, high-value, irreversible, external commitment, privacy-sensitive, or compliance-related actions. For Agent systems, an approval gate is not anti-automation, but a key mechanism that allows automation to safely enter real business operations.

Approval Gate · Operations/Governance

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

That door that is locked only in three situations

There is a narrow bridge in the mountain city, connecting the apothecary and the clinic. On ordinary days, the apprentice delivering medicine can cross the bridge directly, and it is very fast. The shopkeeper knows that most medicine packets are just ordinary herbs, and delaying them would actually harm people.

Later, the pharmacy began preparing potent decoctions. One packet was delivered incorrectly, and the patient nearly had an accident. The elders panicked and ordered that all medicine packets had to line up for a stamp before crossing the bridge, with no exception even for mint water.

For the first few days, everyone felt reassured. But the queue grew longer and longer, ordinary medicines were delivered slowly, and emergency patients waited until they were cold. To save time, the apprentices began mixing several packets of medicine into one basket for approval, and the person stamping could not see clearly what was inside.

The elders added a second seal, requiring one stamp at the bridgehead and one at the pharmacy. The result was thicker documents and more diffuse responsibility. Some people only checked whether the seals were complete, no longer looking at the medicine package itself; truly dangerous decoctions were hidden among piles of ordinary forms and could still slip through.

The old pharmacist watched the line for three days and said the bridge entrance should not slow everything down for all matters. She divided the medicine packets into three categories: ordinary herbs could cross the bridge directly, dosage changes had to be reviewed by a pharmacist, and potent medicines or first-time formulas had to be released personally by the shopkeeper.

She also stipulated that the purpose of stopping something is not to show caution, but to ensure someone can change the decision. If the shopkeeper approves, the reasons must be written clearly; if he refuses, he must also explain how to reconfigure. Apprentices cannot bypass the bridge, and the person stamping the seal cannot just stamp without judgment.

The pharmacy also discovered that what truly needs to be stopped is often not the most expensive medicine, but medicine whose consequences are hard to reverse. If mint water is delivered to the wrong place, it can be redelivered; once a potent decoction is ingested, adding another stamp is meaningless. The old pharmacist also posted the bridge-crossing records on the back wall of the pharmacy. Every intercepted medicine package had to clearly state why it was stopped, who decided, and whether it later caused delays. A month later, she found that some thresholds saved people, while others merely slowed down ordinary medicine. So the thresholds were also reviewed, and unsuitable ones were removed. Later, the pharmacy reviewed thresholds together with medicinal efficacy. If a gate caused urgent medicine to arrive late, it too became a risk, rather than being inherently correct.

After the new rules took effect, the bridgehead became much quieter. Ordinary medicines resumed fast delivery, while dangerous medicine parcels were pulled aside for closer inspection. Occasionally someone complained about the extra gate, and the old pharmacist would point to the river: a gate is not a wall; a gate is what lets the things that should stop stop in the right place.

Reveal

This story is about: Approval threshold

An Approval Gate is a control point in a workflow that requires human approval, policy validation, or permission confirmation before continuing. It is usually used for high-risk, high-value, irreversible, external commitment, privacy-sensitive, or compliance-related actions. For Agent systems, an approval gate is not anti-automation, but a key mechanism that allows automation to safely enter real business operations.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Messenger: an Agent or automated process capable of executing actions
  • Ordinary message passing and organizing: low-risk actions that can be executed automatically
  • Selling off reserved medicinal materials: automation executed a high-impact action without approval controls
  • Three gates: setting different approval strategies by risk level
  • The first door is always open: low-risk tasks require no human intervention
  • The second door half open: medium-risk tasks require condition-triggered approval
  • The third gate is locked: high-risk, irreversible or compliance-sensitive actions must be manually approved
  • Designated owner stamps approval: clarify approval authority and responsibility ownership
  • Knowing which step must pause: the core value of an Approval Gate is risk tiering, not indiscriminate blocking

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

human approvalchange approvalpolicy enginerisk threshold
京ICP备2026014272号