Commit trace

The execution operator starts from a reviewed batch and its approved accepted partition. An operation run records the source revision, operation key and input hash. Ordered steps retain input and output references, status and any external receipt. Execution attempts record attempt number, provider reference and failure reason. These records let the team inspect what happened before deciding to retry.

• Run. Keep the operation key, source revision, input hash and run result.
• Steps. Record ordered actions, input and output references and any external receipt.
• Attempts. Preserve attempt status and provider reference before another execution.

The Execution Operator starts with a reviewed batch and the decision for its exact source revision. The operation run shows which input was used, and the ordered steps show what was sent and returned. Each execution attempt has its own number and status. A target receipt can be attached to a step, while the batch carries the target record reference. Together those records help the operator distinguish a failed attempt from a write whose response was lost.

Agree on the receiving target, its record reference and the receipt that proves a commit completed. A failed or unknown attempt calls for reconciliation against the provider reference. The operator should inspect the run and each step before submitting the same operation again. A completed batch should have a traceable target reference and execution evidence.

Agree which target system receives the accepted rows and how it identifies a completed write. Decide which receipt or provider reference is enough to reconcile an unknown outcome. The Execution Operator should check the operation key and source revision before starting. If a response is uncertain, they inspect the target and retained evidence before retrying; the batch reaches committed only after the outcome is confirmed.

Suppose the target accepts the rows but the response is lost. The attempt may be Unknown while the target already holds the records. The operator checks the provider reference and receipt evidence before any retry. If reconciliation confirms success, they attach the evidence and close the run without producing a duplicate target entry.

Use an attempt whose response was lost after the target accepted data. Compare its operation key, provider reference, step output and receipt with the target record. Record the reconciled result on the run before treating the batch as committed. A repeat attempt should be blocked until this check is complete.

• Commit Ready — Find reviewed batches whose accepted rows can proceed.
• Unknown Attempts — Check attempts that need target reconciliation before retry.

See the related process and the data model to rehearse this handoff with a real submission.