Processing, publication and recovery
Read the discovered function contract before choosing a mutation path. Some operations publish inline in an atomic transaction. Reviewed durable operations separate intent preview, admission, worker execution and publication.
Follow a durable operation
- Record the stable application scope, typed program, dependency order and idempotency key. For previewed work, review the preview and use its token for that exact intent. Numeric and text batch preview binds the applicable metadata, data and policy revisions.
- Capture the job or task ID returned at admission. A worker claims ready work under a lease, checks current authority and applicable revisions, and stages the work when required. Admission and staging are intermediate states.
- Read the committed receipt and the affected data revision. The receipt identifies the published effect. If a parent was cancelled or a job needs inspection, check the scoped result and any child receipts. Earlier units can have committed before cancellation.
Recover when the response is missing
Reconcile using the original caller, scope, key and typed program. For already admitted numeric and text batch jobs, exact replay can return the original job even after the preview expires. Changed intent under the same key conflicts. Use the discovered replay contract for other operation families.
In the reviewed MCP walkthrough, the admission response was deliberately withheld. Replaying the original request recovered the same job, and its receipt and fact readback agreed on one publication revision. Use Tasks and receipts for the operator investigation sequence.