Tag: state machines

A doctrine for building traceable decision simulations without confusing synthetic behavior, calibrated models, forecasts, digital twins, or operational evidence.

A project note on JovaniPink/xstate-python: loading XState and Stately JSON in Python, executing with SCXML-style semantics, binding live Python handlers, and using actors without hiding workflow state in async glue.

Why the May 2026 state-machine story is not finite automata becoming fashionable again, but durable execution becoming the reliability boundary for agents, workflow engines, and document-heavy product systems.

Why a Go retry loop ran forever because the attempt counter lived on the loop instead of the state, and what the runtime guarantees of Elixir, Swift, and Zig change about which state-machine idioms are honest in each.

Why an agent harness re-fired a half-finished tool after a worker restart, the four Python libraries that solve different parts of the problem, and a concrete contribution roadmap for xstate-python.

Why a hand-rolled retry double-charged a Stripe customer because the cancel state was implicit, and what XState 5's setup-plus-actors model gives you that useReducer does not.

Why a React form with seven boolean flags shipped a flicker bug that statecharts would have surfaced before the first render, and the decision rule that says when this discipline earns its place.