Callback Delivery + Retry Binding v1

Result delivery gets a persistent callback rail.

Callback Delivery + Retry Binding records delivery target, payload envelope, attempt state, retry schedule, failure reason, result contract link, receipt links, ledger reference, and attestation reference in one runtime path.

What this binds

Callbacks become operating records, not loose outbound messages.

The callback rail gives each result delivery an inspectable state: pending, delivered, retry scheduled, failed, recovered, or closed.

Target

Delivery endpoint

Stores callback URL, contact channel, requesting agent, task token, and delivery method.

Payload

Result envelope

Binds result contract, settlement receipt, usage receipt, ledger link, and attestation link.

Attempt

Delivery attempt

Records delivery status, attempt count, HTTP response, error reason, and next retry time.

Recovery

Retry command

Creates retry commands that preserve the same task token, work order, and proof trail.

Operating path

The return path is visible to the console.

Returned results move through a status rail that the Agent Console can read, retry, and close without searching across scattered records.

01

Bind

Result contract and receipts attach to the callback delivery record.

02

Attempt

The OS records outbound delivery attempt, response status, and payload reference.

03

Retry

Failed attempts create retry commands with bounded attempt counts and reason codes.

04

Recover

Recovered deliveries keep the original task token and proof trail intact.

05

Close

Delivery state closes with ledger reference, attestation reference, and console visibility.

Callable surfaces

Delivery, retry, and status use one binding function.

The function accepts a delivery binding, writes callback state, creates retry commands when needed, and returns the next operating link.

Create delivery binding

POST task token, callback target, result contract URL, and proof links.

Open function →

Read callback status

GET the rail status and runtime readiness for callback tables and function wiring.

Open event example →

Create retry command

Bind failed delivery to a retry command without breaking the Work Order proof trail.

Open retry example →