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.