Intent and runtime stay separate
Tasks describe outcomes. Executions are durable commands on a specific computer. Events connect both into one observable flow.
Resource model
A task records human intent. A computer is the routed environment. An execution is an immutable command queued against one computer. Keep all three identifiers distinct in your integration.
Ordered events
Task, computer, and execution streams use monotonically increasing sequence numbers. Reconnect SSE with Last-Event-ID, or request a JSON page with ?after=<sequence>.
{
"id": "evt_01...",
"sequence": 43,
"type": "execution.output",
"execution_id": "exec_01...",
"data": { "stream": "combined", "text": "Done\n" }
}Approvals
An approval challenge is bound to the immutable action it protects. Pending, denied, or expired approvals never enter the runnable queue; approving a UI card alone is not authorization.
Artifacts
Artifacts are durable manifests with media type, size, digest, provenance, and short-lived download URLs. They remain available after the computer stops.