Examples¶
Runnable machines in the repo. Pair each app with the guide pages that name the same machinery.
| Example | What it shows | Pair with |
|---|---|---|
| state_machine_walkthrough | A small transition table; guards and actions kept with the spec; pure machine-transition tests; the same machine value in the browser and on the JVM |
First machine, The table |
| nine_states | Parallel regions for orthogonal UI axes; tags as render semantics; a render-priority table; one view branch instead of a cross-product |
Parallel regions, Tags |
| long_running_work | A parent :spawn-all of N workers; :join :all; progress as an internal self-transition; cooperative cancel and teardown on every exit |
Actors, Automatic transitions |
| websocket | Hierarchical connection states; a :spawned socket actor; :after exponential backoff; :always queue flush; tags for status; :current-socket? drops events from a replaced socket |
Hierarchical states, Actors, Automatic transitions |
Not a machine example: process_monitor_helix¶
Useful for seeing another rendering substrate consume subscriptions, but it is not a machine example. Do not use it to learn the FSM API.