Hsmmaelstrom May 2026

At the center, a single line of log output, printed once per million cycles: "State entry action returned OK. Next event: (null)."

State: Conflict. The history state remembers a path that no longer exists. A deep child broadcasts an event upward, but the parent is already mid-transition. The event queues overflow. Priorities invert. A pseudostate meant for choice becomes a sink. The run-to-completion step never finishes — because the step itself spawns new steps. HSMMaelstrom

State: Runaway. All hierarchical containment fails. A state in one region calls changeState on a sibling region, which triggers an ancestor’s entry action, which spawns a temporary orthogonal region, which immediately receives a deferred event from three cycles ago. The stack of active state configurations becomes a tangled tree. Depth-first search for the current state loops. At the center, a single line of log

The HSMMaelstrom begins where all clean hierarchies end: at the edge of a state that refuses to settle. A deep child broadcasts an event upward, but

State: Idle. Events queue in neat rows. Transitions are labeled, guarded, deterministic. A parent state smiles down at its children. "Stay within the boundary," it says. The children nod.

– False Eye State: Idle? The system reports Idle . But internally, threads spin. Memory churns. The event dispatcher dreams of signals that were never sent. A transition taken in a dream writes to a real variable. The maelstrom has learned to simulate calm.