ADACTION
DOCK
Checking service

USE CASE 05 / DURABLE CONTROL

THE AGENT
KEEPS GOING.

An external agent owns the goal and sequence. ActionDock turns each requested operation into a durable job and returns verifiable state for the next reasoning step.

01AGENTChooses one bounded action
02ACTIONDOCKValidates policy and queues work
03EVIDENCEPersists result and terminal state
04AGENTConsumes evidence and continues

THE EXECUTION CONTRACT

One action.
One durable result.

ActionDock is not a hidden orchestrator. It is the control boundary that makes long-running agent work recoverable and inspectable.

01

Discover exact capabilities

The agent reads live JSON Schemas and side-effect flags instead of guessing what the service can do.

list_actions · list_connections
02

Create an idempotent job

A stable key makes a retry resolve to the same request. Shared workflow metadata groups the sequence without moving orchestration into ActionDock.

run_action
03

Stop at the write boundary

An external write exposes its exact method, path, query, and body before anything changes.

workspace owner · dashboard approval
04

Return durable evidence

A signed callback or authenticated poll returns the terminal job, structured result, report artifact, and actionable error.

wait_for_job · list_events

CLEAR OWNERSHIP

Reasoning stays with the agent.

EXTERNAL AGENT

Defines the outcome, chooses the sequence, interprets results, and decides whether to continue.

ACTIONDOCK

Validates inputs, applies policy, executes one action, preserves evidence, and returns state.

WORKSPACE OWNER

Controls API keys, connection secrets, destination allowlists, approvals, callbacks, and billing.

MCP OR HTTP

Give your agent a reliable action boundary.

Connect an agentView plans