Simulation Runs

The model describes the process. A run records what happened when a reviewed revision was executed with a scenario. The Simulation Operator can inspect the operation key, frozen source revision, start and completion dates, result reference and failure reason. Individual steps provide their own sequence and input and output references. That separation makes a result explainable without rewriting the model that produced it.

For an intake model, a run may complete the initial node and then wait for a response from an external action. The attempt ledger records triggered operations against the operation key. A step can retain an external receipt ID, source, receipt date and evidence attachment. The Independent Reviewer can check the receipt against the completed step before the run is treated as successful.

• Run identity. The operation key and source revision identify the attempted work.
• Step trace. Numbered steps retain action names, timing and input and output references.
• Attempt history. Separate attempts show retries and unknown outcomes without hiding the earlier event.

Decide how an operation key is formed and who investigates a repeated key. Establish which external source supplies a receipt and what counts as verified effect. The run should be marked Succeeded only after that verification, so the team must know who will inspect evidence and where it will be attached.

Agree how failures and uncertain outcomes are escalated. A Failed step needs a reason and a clear next action. An Unknown attempt needs reconciliation against the external source before another action is triggered. The Process Owner and Simulation Operator should know when a run stays open, when it requires reconciliation and when a correction workflow should supersede an executed revision.

Choose a reviewed intake model and run it under its linked scenario. Inspect the source revision on the run, then compare the completed step list with the intended node order. Find the input and output references for the specialist handoff. Ask the Evidence Steward to verify the external receipt and record the document that supports it.

Rehearse a failed external response as well. Confirm the attempt shows its failure reason and that no successful result is claimed from an unverified effect. Rehearse an unknown response and let the team investigate it before retrying. The result of the exercise should be a trace a new reviewer can follow from model revision to operation, step, receipt and final decision.

• Run timeline — Inspect runs by status and start and completion dates.
• Runs requiring reconciliation — Find operations whose effects need investigation.
• Failed or unknown attempts — Check provider references and failure reasons before retrying.

Follow simulation execution from reviewed model to result, then correction and follow-up when a run needs repair.