state-machine-simulation
State Machine Simulation
Model supplied behavior as a static Mermaid state diagram for inspection and learning by default, with an optional graph-only, event-driven browser app in which users emit modeled events and watch the active state and transition update live. Neither output executes the target, performs its side effects, modifies its sources, or presents inferred behavior as observed runtime behavior.
Inputs
A. Target
A required inline or repository-relative workflow, procedure, algorithm, function, or skill in prose, pseudocode, source code, or Markdown. An entry point is also required when the source defines multiple operations. The target is read-only and authoritative for states, transitions, guards, actions, outputs, and errors.
B. Scenario
Optional initial arguments, machine context, environment values, and expected external responses. Values the user does not supply remain symbolic; the machine model must preserve source-feasible outcomes as explicit events or finite event payloads rather than silently inventing them. When HTML is selected, the app must let the user emit those modeled choices.
C. Supporting context
Optional available definitions for callees, procedures, data shapes, invariants, and external behavior. Relevant context accompanying a target path is required input, but it may explain rather than override the target; surface conflicts and preserve the target's behavior.