User Intent, Constraints, and Approval

Definition

User intent defines the target outcome. Constraints define hard boundaries for behavior. Approval gates define where human authority is required before progressing or executing external actions.

Why it matters

Clear intent and constraints reduce ambiguity, while approval checkpoints prevent high-impact mistakes from being executed without review.

When to use

Use explicit intent/constraint/approval framing whenever workflows involve sensitive data, irreversible actions, or quality thresholds that require accountable review.

When not to use

For low-risk internal drafts and read-only exploratory tasks, dense approval layers can slow work without meaningful risk reduction.

Failure modes

Failure appears as broad goals with missing constraints, unclear rejection criteria, or approvals placed too late in the workflow to prevent risky actions.

Related pages

Planner-Driven vs Event-Driven Orchestration · Support: Triage and Escalation Swarm · Scope Agent Permissions Safely

Common questions

What is the difference between intent and constraints? Intent defines the outcome goal; constraints define what methods are allowed to reach that goal.

Where should approvals happen? Place approvals before external side effects and at major risk transitions, not only at final output.