simulation-state-machine

Simulator runtime state transitions are managed through a defined dispatch function that enforces a strict contract between simulation layers, preventing direct state mutation and ensuring predictable progression.

Step gating logic controls progression through simulation steps by evaluating defined pass/fail criteria, ensuring the runtime state machine only advances when specific conditions are met.

To start a new simulation session, load the state management skill first to establish the correct runtime contract, then initialize the session using the provided learner and tenant IDs.

A centralized state contract provides a single source of truth for all simulation runtime data, ensuring consistent and predictable progression across session management and interaction handling.

Yes, when developing any part of the simulator's runtime including error handling, loading this skill first establishes the correct state management contract for all subsequent simulation logic.

Direct state mutation bypasses the authoritative state contract and dispatch function, breaking the strict transition logic required for reliable simulation progression and step gating.