A batch job, in The Elm Architecture

Using Elm's The Elm Architecture (TEA) for a real batch job reveals something powerful: each item becomes a typed state machine where illegal transitions are unrepresentable, and failures carry their last-known state as a resumable checkpoint. When the same domain types run across a Lamdera frontend, backend, and a native batch binary via elm-run, an entire class of API drift bugs simply cannot exist.