Operations control

An Operation Receipt records an operation key, action, expected revision, result state, time and parent instruction. It can also hold an external reference, effect references and a failure reason. Pending, Completed, Failed and needs review are distinct outcomes. This gives operations staff a durable record when a provider response is delayed or a command cannot be safely completed.

The receipt belongs beside the instruction and its execution evidence. A receipt marked Completed establishes what the guarded action recorded; the reviewer still needs to check the provider evidence and the instruction state. A needs review receipt calls for an explicit discrepancy and owner. The stable operation key helps distinguish a retry of the same action from a conflicting request.

• Record. Keep a receipt tied to the instruction, revision and action that triggered it.
• Investigate. Compare an unresolved receipt with the parent instruction, provider acknowledgement and execution events.
• Close. Mark the known result only after the evidence supports it, or retain needs review with a concrete reason.

Name the people who monitor unresolved work and define when they escalate to the authorized provider. Decide how long a pending acknowledgement remains in the queue before review. Preserve operation keys across retries and use the expected revision to detect a changed source record. Agree where an external reference is obtained and who records the final determination.

A team should rehearse both a clean acknowledgement and an uncertain one. The uncertain case matters because a new submission could duplicate an external action. The safer sequence is to read the receipt, inspect the provider’s reference and execution evidence, and document the result against the same instruction.

Take an authorized instruction and start a provider submission. Inspect its operation key and expected revision. In the normal case, match the provider acknowledgement and evidence, then reconcile the receipt to Completed. In the exception case, withhold the acknowledgement, leave the receipt Pending or needs review, and ask the reviewer to compare the provider state before any retry. Change the instruction revision and confirm that an old operation cannot be mistaken for a command against the new version. Retain a concrete failure reason when the action fails.

• Unresolved Operations — Pending, failed or review-needed actions with their parent and reason.
• Open Instructions — Current request states to compare against a receipt.
• Pending Evidence — Provider events that may explain an unresolved outcome.

Use provider reconciliation and completion checks.