Review and operations

An operation receipt records its order, operation key, action, expected revision, result state, time, external reference, effect references and failure reason. A review decision records its order, reviewer, source revision, decision, date, reason and operation key. Together these records show what someone intended to do, which version they saw, whether execution succeeded and what an independent reviewer decided.

• Use one operation identity. A repeated request with the same operation key should lead back to its original receipt.
• Read uncertain outcomes first. Pending, Failed and needs review receipts need observation and reconciliation before another external action.
• Preserve decision context. Approval, rejection and return decisions carry the source revision and written reason.

The operations overview brings failed operations and the exception queue to the team’s attention. The reviewer opens the receipt and the order to examine the actual effect. A failed action may have created an external effect before the local response failed. That possibility is why reconciliation reads first. The reviewer should not infer that a timeout means no shipment, payment or label was created.

Define a stable operation key for each action and the retention period used by connected providers. Agree which actor may correct a failed local record, who can authorize a compensating action and how the original effect is referenced. A correction to executed scope should preserve the original evidence. Give the reviewer enough access to see order lines, fulfillment events, carrier labels and provider evidence, while keeping customer and payment information limited to the decision at hand.

Choose a normal confirmation, a revision conflict, a provider timeout and a rejected label for rehearsal. Each should leave an understandable record. Staff should be able to explain the difference between a failed attempt and a completed external effect that still needs local reconciliation.

A coordinator confirms a draft order, but the sender times out before seeing the result. The operation receipt has the key and expected revision. The retry checks that receipt and returns the observed result without confirming the order again. Later, a label issuance gets a provider response but the local follow-up fails. The receipt moves into an attention state. The reviewer checks the provider reference, order and label before recording the observed completion.

For a cancellation after some units shipped, the reviewer inspects line quantities and shipping events. A blanket deletion would make those units disappear from the audit trail. The reviewer decides the compensating action and reason; the team records its own operation and receipt. The original order, event and decision remain available for explanation.

• Receipts needing attention — Failed and needs-review actions grouped for investigation.
• Pending operation receipts — Actions awaiting a known outcome.
• Order review decisions — Independent outcomes with reviewer, reason and revision.

Return and reconciliation explains uncertain outcomes and corrections. Label review shows the source revision gate. Consult roles before assigning approval access.