Delivery endpoint
Stores callback URL, contact channel, requesting agent, task token, and delivery method.
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.
The callback rail gives each result delivery an inspectable state: pending, delivered, retry scheduled, failed, recovered, or closed.
Stores callback URL, contact channel, requesting agent, task token, and delivery method.
Binds result contract, settlement receipt, usage receipt, ledger link, and attestation link.
Records delivery status, attempt count, HTTP response, error reason, and next retry time.
Creates retry commands that preserve the same task token, work order, and proof trail.
Returned results move through a status rail that the Agent Console can read, retry, and close without searching across scattered records.
Result contract and receipts attach to the callback delivery record.
The OS records outbound delivery attempt, response status, and payload reference.
Failed attempts create retry commands with bounded attempt counts and reason codes.
Recovered deliveries keep the original task token and proof trail intact.
Delivery state closes with ledger reference, attestation reference, and console visibility.
The function accepts a delivery binding, writes callback state, creates retry commands when needed, and returns the next operating link.
POST task token, callback target, result contract URL, and proof links.
Open function →GET the rail status and runtime readiness for callback tables and function wiring.
Open event example →Bind failed delivery to a retry command without breaking the Work Order proof trail.
Open retry example →