University of Michigan - Ann Arbor

In StateM, each execution maintains an isolated, mutable runtime record that is strictly decoupled from the static, reusable runbook. For every individual run, StateM tracks and persists:

- A unique run identifier
- The current active state and current state-entry identifier
- The complete transition history across states
- Execution outcomes of all lifecycle hooks and before-transfer checks
- Event timestamps
- File references to state-local evidence artifacts

Separating the mutable per-run record from the static control profile ensures that multiple concurrent runs or distinct agents can operate simultaneously under the same runbook without conflating their procedural progress.

StateM Per-Run Execution Record

How does StateM track state-local evidence artifacts generated during an individual execution?

In StateM, separating the mutable per-run record from the static control profile ensures that multiple concurrent runs can execute using the same runbook without conflating their procedural progress.

Learn Before

Related