Operations evidence

Each operation receipt carries a stable key, expected revision, action, result state and references to its claimed effects. The team uses the receipt to distinguish a pending operation from a completed one and to see why a failure or discrepancy needs review. Evidence stays attached to the parent instruction.

• Identify the work. Use a stable operation key and expected revision for each receipt.
• Keep the evidence. Keep references to the effects the operation claims to have produced.
• Handle the result. Move a receipt to needs review with a reason when a claimed effect is missing.

Agree how effect references point to persisted local records and how an external reference is checked. A repeat request with the same key should not create a duplicate financial effect. A receipt should be marked completed only after the claimed records can be found; otherwise the discrepancy belongs in the failure reason.

Agree how the Accounting Reviewer locates each claimed local effect. Keep the operation key stable across retries and preserve a failure reason when an effect is absent. Verification reads existing records; it must not submit the provider instruction again.

Take a submitted instruction with a receipt whose effect references point to its decision and provider event. Confirm those records exist before accepting completion. Then rehearse a missing effect reference; keep the receipt in review with a concrete reason and avoid resending the provider instruction as a side effect of verification.

Take a receipt for a submitted instruction and inspect its decision and provider event references. Mark it Completed only when the claimed local records exist. Remove one referenced effect in a rehearsal and record the discrepancy as needs review. Repeat the same operation key and confirm it does not issue a second provider action.

A receipt marked Completed must correspond to persisted local effects. A receipt marked Failed needs its failure reason; needs review points to a discrepancy the Accounting Reviewer can investigate. Keep the original operation key when retrying a read so the same action is recognized rather than issued again.

• Operations needing review — Show Pending, Failed and needs review receipts with their reasons.
• Provider evidence — Inspect verified provider lines related to the instruction.

Follow the instruction lifecycle for the complete handoff. Use implementation to agree provider evidence and access before the first live cycle. The data model lists the parent and related records to prepare for migration.