Execution provenance

Operation runs hold the operation key, source revision, input hash, status, result reference and failure reason. Operation steps record each numbered action with input and output references and any external receipt evidence. State history attaches a status transition, actor, time, reason and operation key to the stream.

• Run. The Operations Analyst checks the operation key, frozen revision and result reference.
• Steps. Each numbered action records its status and input and output references.
• History. The Stream Owner compares the current status with recorded transitions.

This trail helps the reviewer separate an attempted action from a confirmed effect. It also connects a metric result to the exact run that produced it, so a replacement calculation does not erase the earlier answer.

Agree how repeated operation keys are handled and when a run requires reconciliation. If an external step returns an unknown result, inspect the receipt before retrying. Define who may correct an executed revision and how the successor is identified.

Rehearse a repeated operation key and a run whose effect needs reconciliation. The Operations Analyst should distinguish the existing run from a new attempt and inspect any step receipt. The Stream Owner checks the status transition and source revision before making a correction.

Suppose a run shows a changed stream but its final read-back failed. The analyst inspects the numbered steps, compares the result reference to the stream and determines whether the effect exists. They keep the run observable until reconciliation resolves it. If a correction is needed, the owner increments the stream revision; the earlier run and history remain intact.

Ask the Operations Analyst to trace the correction from the source revision to its run, numbered steps and state history. If a metric result is involved, compare the original run and result with the successor rather than overwriting the first calculation.

For a rehearsal, select one successful run and one run needing reconciliation. Have the analyst identify the input hash, source revision and result reference in each. The distinction should remain clear when the stream has already moved to a later revision.

• Runs needing reconciliation — Runs whose outcome needs an analyst to investigate.
• Stream status board — Current stream states for comparison with recorded history.

See the related process for the handoff and the data model for the connected records.