Operations control

Operations Overview ranks recorded exceptions across instructions, execution evidence and operation receipts. operation receipts stores a stable operation key, expected revision, outcome, external reference, effect references and failure reason under an instruction. The record helps the team check whether an attempted action completed, failed or needs review.

• Record. A receipt marked Pending is a question to investigate. The team reads the claimed effect references against the actual local records before marking it Completed. If an effect is missing or inconsistent, needs review keeps the discrepancy visible. Repeating the same operation key should return to the original outcome rather than creating another provider action.
• Decision. Agree which operator handles each exception and when it must reach an independent reviewer. Keep organization membership, active counterparties and account access current. App Administrators maintain these scopes but cannot use that role to award themselves a financial decision.
• Evidence. Retain the operation key and concrete discrepancy with the instruction so a later reviewer can distinguish a failed effect from an unknown one.

Agree who investigates a receipt in needs review and when the Independent Finance Reviewer must inspect a financial effect. Keep organization membership and active counterparties current, but do not give administrators reviewer authority through configuration access. Choose one provider timeout and one missing local effect for the pilot. Check the receipt against the provider reference and actual linked rows before treating an action as completed. Record the discrepancy in the failure reason so another operator can continue the inquiry.

A provider request times out after an instruction is sent. The analyst opens the receipt and external reference, checks for a persisted provider ID and execution evidence, and asks the provider to clarify the result. The team does not send a new instruction merely because the first call timed out. At handoff, the next analyst should see the operation key, expected revision, action, result state and external reference together. They can then inspect the claimed effects under the instruction and explain whether the provider outcome is known. A repeated request with the same key should lead back to that same receipt. The Independent Finance Reviewer checks any financial consequence before the case is closed.

• Receipts needing review — Investigate recorded discrepancies and claimed effects under the parent instruction.
• Active counterparties — Check current eligibility and organization scope before another instruction is prepared.

Follow instruction review, provider confirmation and account reconciliation to see how this work joins the next stage.