Deep report preview
A category report on how human approval, delegation windows, renewal, and runtime leash enforcement should work in serious agent systems.
Scope
Methodology
Anchored the report in official workflow and identity documentation from Microsoft, Cloudflare, Oracle, and Passage, with dates stated as of March 22, 2026.
Used one Perplexity deep-research run plus four focused search queries to map approval stages, resume behavior, renewal controls, and step-up authentication patterns.
Separated approval, delegated runtime authority, resume, renewal, and publish into distinct operator decisions instead of collapsing them into one generic authorization model.
Preferred explicit denial reasons, operator tradeoffs, and unattended-subscription controls over abstract governance language.
Sources
Official guide for human approval checkpoints inside agent workflows.
Open source →Official multistage and AI approval documentation useful for stage-aware creation controls.
Open source →Workflow pause, approval, timeout, and escalation model for long-running agent systems.
Open source →Useful distinction between temporary delegation and true ownership transfer.
Open source →Reference for requiring fresh user presence on sensitive actions even inside an active session.
Open source →Application-level view of why authorization needs to persist across workflow state transitions.
Open source →Useful guardrail framing for no-privilege-escalation, scope inheritance, and delegation depth.
Open source →Workflow-stage identity and separation-of-duties framing for governed agent execution.
Open source →Operational discussion of delegated approval behavior and managed approval state.
Open source →Research framing for hard and soft runtime constraints in long-running agent execution.
Open source →Key findings
Approval and leash mechanisms solve different problems and should be shown separately in both policy and UI.
Resume is a distinct risk surface because it combines recovery with renewed authority.
Recurring subscriptions need explicit renewal UX, runtime denial reasons, and delivery visibility.
The strongest pattern is stage-aware approval paired with runtime leash scope enforcement and fresh step-up for publish or release.
Dataset summary
Preview excerpt
The full report maps approval stages, delegation windows, denial reasons, and renewal patterns into a practical governance model for agent systems.
Sample rows
Artifacts
Human-readable dossier with the full authority model, examples, and recommendations.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/markdown
Structured workflow-stage authority rows, source mappings, and governance summary metrics.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/json
Structured chart payload backing the inline report visuals and machine-readable consumers.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/charts
Saved report definition artifact.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/definition
Structured evidence ledger tying claims and chart provenance back to cited sources.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/evidence
Structured methodology notes, dataset summary, and report timing metadata.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/methodology
Structured source ledger with source kinds, labels, notes, and URLs.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/sources
Single purchase target returning the markdown report, JSON artifact, and manifest together.
Endpoint: /api/reports/agent-approvals-and-human-leashes-2026/bundle
About
Saved plan changes are reviewed separately from evidence changes. Query entries become live query runners, and research prompts become grounded prompt runs during create and refresh.