Discussion Gate
person concept tool org talk claim — click a node to jump to its page; hover an arrow for the relation
A discussion gate is a designated checkpoint within a large agentic workflow where execution is paused and human review or deliberation occurs before the process continues. It is considered a critical structural element of the Ask-Plan-Audit-Build-Verify Workflow.
Core Concept
The term is introduced in the context of designing robust, long-running agent pipelines. The core insight is that practitioners must consciously identify where in their workflows these gates should be placed — they do not emerge naturally but must be deliberately engineered. As stated in the source talk: "know where your discussion gates are in your large workflows." To Give an Agent a Workspace: Laying a Foundation for Messy Forever Work, 29:02
Role in Agentic Workflows
Discussion gates serve as the human-in-the-loop mechanism within otherwise automated pipelines. Rather than allowing an agent to proceed end-to-end without oversight — which risks compounding errors across many steps — a discussion gate forces a pause at a meaningful juncture (e.g., after planning but before building, or after auditing before further action). This maps directly onto the Ask → Plan → Audit → Build → Verify structure, where transition points between phases are natural candidates for a gate. To Give an Agent a Workspace: Laying a Foundation for Messy Forever Work, 29:02
Design Implication
The framing of discussion gates as something practitioners must know where to place implies they are an architectural decision, not a default behavior. This suggests that a key skill in agent engineering is analyzing a workflow's risk and complexity profile to determine which transitions warrant mandatory human deliberation versus which can be left to autonomous execution.