Delivery and receipts

A decided funding case can lead to a delivery action. Operation runs connect the case revision to an operation key, input hash, result reference and outcome. Execution attempts record each attempt’s number, start and finish, provider reference and failure reason. Receipts preserve ordered steps within a run, including an external receipt ID or attached evidence where the connected service supplies one. These records let the team answer whether an action was attempted, whether it succeeded and which source revision it used.

The distinction between a local decision and a confirmed external result is practical. A case may be Decided while its run is Queued or Running. An attempt can be Failed or Unknown and require investigation. A run marked reconciliation required deserves a human check against the external reference before anyone treats the case as delivered. The case’s delivery reference and Delivered state should follow confirmed evidence, not a hopeful button press.

• Run. The operation key and source revision identify the approved action being executed.
• Attempt. Each execution attempt records timing, provider reference and any failure reason.
• Receipt. Ordered receipt steps preserve input, output and external acknowledgment for the run.

Decide which external service performs the action for each program and which returned reference counts as confirmation. Agree who checks a failed or unknown attempt and who can reconcile a result that may have completed outside the app. Before retrying an uncertain action, compare its operation key and provider reference with the earlier attempt. A new revision requires a deliberate decision about whether it represents a new action or a correction to an earlier one.

Review the evidence format for external receipts before go-live. A receipt may hold an ID, source, date and attached proof. The program team should be able to find that proof from the selected case workspace. The Auditor needs a read path through the run and its receipts while the Program Officer needs a clear way to see exceptions without changing historical evidence.

Start with an approved request for a community facility upgrade. Record its decided case revision and follow the operation run. Check that the attempt refers to the same case and that the receipt shows the action and external acknowledgment. Then simulate an uncertain provider response. The team should see the Unknown attempt or reconciliation state and investigate the external system before marking the case Delivered. On a retry, inspect the operation key and receipt sequence to make sure one successful action is not counted twice.

• Receipt timeline — Ordered action steps with start, completion and result state.
• Operation exceptions — Failed or reconciliation-required runs that need investigation.
• Funding status board — Decided cases awaiting a confirmed delivery result.

See delivery tracing for the full handoff and correction and follow-up when a delivered revision changes.