Delivery operations

When an approved case has an uncertain delivery result, start by agreeing the operation key, source revision and provider reference. The operator traces the original operation key and attempt before considering any repeat. The run records the source revision, while each step and attempt shows what happened during delivery.

The operator starts a run against the approved source revision. Its steps retain action order, input and output references and any external receipt. Execution attempts retain attempt numbers and provider references. The team can locate the specific attempt behind a result rather than treating a successful local step as proof of delivery.

• Queue. Start the operation against the approved source revision and retain its key.
• Trace. Follow ordered steps and attempts through their provider references.
• Reconcile. Resolve an Unknown result against the original attempt before counting delivery.

A provider timeout or unknown result stays in reconciliation. The team checks the original attempt and receipt before sending again, so a retry does not create an unexamined duplicate. The handoff is a change in responsibility, not simply a new label. Agree who can prepare, verify and decide before inviting users into the operating team.

Choose the authorized delivery channel and agree who can inspect its provider receipts. Set the rule for matching an operation key, source revision and provider reference; the same case can have more than one revision. Decide who investigates a timeout and when a repeat attempt may be considered. Keep credentials and channel setup with the operating team responsible for delivery.

Rehearse a run whose local step succeeded but whose external receipt is absent. The case remains short of confirmed delivery while the operator checks the original attempt. Confirm that a subsequent attempt retains its own attempt number and that the run history shows which result was reconciled. A delivered count must be explainable from provider acknowledgment.

Take an approved case whose delivery attempt has an unknown result. Enter the source details and inspect the case in the workspace. Follow the related evidence into review, then compare the approved revision with the operation that carries it forward. Delivered count changes only after confirmation. A successful local step without a correlated external receipt is a reason to inspect the run, not a reason to mark the case delivered. A colleague should be able to explain the final state from the stored case, decision, history and receipt without asking the original operator.

Rehearse an Unknown attempt followed by a delayed provider receipt. Match the receipt to the original operation key before any retry. Check that the run records the reconciled result and that the case changes to Delivered only after confirmation. If no confirmation arrives, leave the exception visible for the operator.

• Delivery reconciliation — Runs whose original provider outcome still needs to be resolved.
• Uncertain attempts — Attempts marked Unknown with their operation key and provider reference.

Follow this case through its process. Review roles before widening access.