Execution and history

An approved matter may require a delivery action. Operation receipts keeps the run name, operation key, source revision, input hash, status and persisted result reference. Operation steps records each ordered action with its input, output and external receipt state. Execution attempts records attempts, provider references and failure reasons. Together these records help the team see whether an action was queued, running, succeeded, failed or needs reconciliation. A proposed outcome is not the same as a confirmed external result.

State history records status changes for the matter with the old state, new state, actor, time, revision, operation key and reason. The history connects the visible case status to the action that changed it. A later correction can preserve the original transition and operation evidence while introducing a successor revision. That allows an Auditor to reconstruct what the team knew and did at each decision point.

• Operation receipt. Keep the approved revision and result reference with the run that acted on the case.
• Step trace. Review ordered actions and any external receipt before interpreting a run as complete.
• State history. Read the transition and its reason beside the current matter status.

Agree what counts as a durable delivery result and which external source provides its reference. Define when a failed operation may be retried and how the team checks an uncertain provider outcome first. An unknown attempt or a receipt marked for reconciliation requires investigation with the source of delivery. Decide who is responsible for that check and where the confirmed reference is recorded. The operation key should let the team recognize a repeated attempt against the same approved action.

Suppose a reviewed matter is ready for delivery, but the external destination times out. The operation receipt shows the run and its input revision, while the attempt records the uncertain provider result. The coordinator checks the destination’s receipt before retrying. If the external action succeeded, the team records that result against the original operation. If it failed, the failure reason and next attempt remain traceable. Either way, the case history should explain the final status.

Start from a closed matter and follow its delivery reference to the operation receipt, steps and attempts. Compare the receipt’s source revision with the approved review decisions record. Check whether the step has an external receipt or whether the result requires reconciliation. Then read state history to see which actor and operation key changed the matter status. A status label alone is an incomplete delivery check.

Repeat with a superseded outcome. The original receipt and steps remain available, while the changed revision goes through review again. The compensating deadline tells the team what follow-up still needs ownership. This gives the case owner a practical answer when asked why an earlier result changed.

• Operation exceptions — Failed and reconciliation-required runs needing investigation.
• Decision history — The reviewed source revision to compare with a run.
• Closed matters — Completed cases with their delivery references.

Follow outcome delivery and correction review to see how execution evidence remains attached to the case.