Delivery and execution

Once an item has a decision, its delivery reference tells the team which external result belongs to it. The content item retains its completed date and status. The execution trail adds detail: an attempt records an operation key, attempt number, timing, provider reference and failure reason. A run retains the source revision, input hash and result reference. Ordered steps show the action, input and output references, receipt identifier, source and evidence. These records let an operator investigate the actual outcome rather than treating a Delivered label as the entire story.

A repository transfer may return an uncertain result. An Unknown attempt or step is a reason to inspect the provider reference and receipt before trying again. A run marked reconciliation required tells the team that the recorded result needs investigation. The operation key and source revision help connect the follow-up to the original action. The Content Items and Details workspace shows the operation run and step trace beside the selected item.

• Item retains the delivery reference. The receiving result can be found from the content record.
• Attempts remain separate. Each execution attempt keeps its sequence and outcome.
• Steps preserve receipts. External receipt details explain what happened within a run.

Define where the delivery reference comes from and when it is considered final. Agree which external endpoint receives the content and what acknowledgement it returns. Map the provider’s identifiers to the operation key and result reference. A successful local step should not be mistaken for external acceptance; the receipt evidence and provider reference are the useful reconciliation anchors.

Decide who investigates Failed, Unknown and reconciliation required outcomes. Keep a sample failed attempt and a sample accepted receipt for a rehearsal. Agree how a corrected revision is sent after an earlier delivery and what compensating task is required if the earlier result must be superseded. Project policy should identify who authorizes the handoff after review.

A reviewer approves a content revision. The operator records its delivery reference after the receiving system responds. The run shows the revision and result reference; its steps show the output and external receipt. Later, another item produces an Unknown attempt. The administrator checks the recorded provider reference and receipt against the receiving endpoint, then asks the authorized execution process to retain the reconciliation evidence. The team does not infer success from the content status alone; the run and receipt explain what was accepted.

• Delivered content — Items with completion date and delivery reference.
• Runs requiring reconciliation — Run results that need investigation against the external receipt.
• Failed execution attempts — Attempts with failure reasons and operation keys.

Decision to delivery follows the external handoff. Correction and supersession covers a changed delivered item.