456
Prompt

Autonomy Boundary Prompt

Defines exactly what an agent may do alone, with approval, or never.

1 min readupdated 2026-08-01

/ quick answer

Run before promoting any workflow from human-triggered to autonomous. Defines exactly what an agent may do alone, with approval, or never.

Defines exactly what an agent may do alone, with approval, or never. Run before promoting any workflow from human-triggered to autonomous. Copy the prompt below, swap the bracketed variables for your own context, and run it in any capable model. This prompt node is part of the Onexial knowledge graph and links to related concepts, workflows and tools below.
Context
Run before promoting any workflow from human-triggered to autonomous.
Prompt
Act as a risk officer for AI automation. For the workflow below, produce a three-column policy table:

AUTONOMOUS | REQUIRES APPROVAL | NEVER

For each action include the reasoning and the blast radius if it goes wrong. Then define:
- escalation triggers (confidence, cost, ambiguity, repeated failure)
- the exact data an escalation must contain
- audit and logging requirements
- the kill-switch procedure

Workflow: {{WORKFLOW}}
Systems touched: {{SYSTEMS}}
Regulatory context: {{REGULATION}}
Example Output
AUTONOMOUS: tag ticket, draft reply, look up order. REQUIRES APPROVAL: refund <$100, change subscription...
Related Workflow
Related Tool Stacks
/ frequently asked

What does the Autonomy Boundary Prompt prompt do?

Run before promoting any workflow from human-triggered to autonomous.

Which AI models work with this prompt?

It is model-agnostic: it works with any capable general model. Replace the bracketed variables with your own context before running it.

What output should I expect?

AUTONOMOUS: tag ticket, draft reply, look up order. REQUIRES APPROVAL: refund <$100, change subscription...