Closing talk of wroclove.rb 2026 by Julik Tarkhanov. Motivated by a money-transfer workflow (retry, idempotency, background scheduling, emails, error handling), Julik defines a workflow as steps depending on each other's completion/failure with persisted state. Argues that mainstream 'durable execution' offerings — Cloudflare Workflows ('orange cloud man') and Durable Objects/Temporal/Restate ('black pyramid man') — sell a deception: imperative code pretending to be a DAG, glued together by opaque persistence tricks (overriding performance.now, date/time etc.) on Firecracker VMs. A truly durable function would require a Smalltalk-style VM able to serialize call stacks, DB connections, sockets, tokens and transient state — which no mainstream runtime provides. Better model: treat workflows as DAGs explicitly, like Houdini scenes, Nuke compositing, Terraform state (HCL + provider modules) or Excel formulas — where the DAG and the executable node code are kept separate. Reviews Temporal's Ruby bindings, acidic_job (Stephen Margheim), HYA (Honey Badger) and Active Job Continuation (Rails 8.1 / 37signals) as examples of DAGs smuggled inside `perform`. Presents Geneva Drive: Rails-native, Active Record-backed workflows with step/wait DSL, polymorphic hero association, instance-evaluated step blocks, flow control (cancel!, finish!, skip, reattempt, pause), per-step fine-grained locking, executes on existing active-job adapter, works on SQLite/MySQL/Postgres. Demo inside Kora (email assistant) plus Porsche TUI (Stas). Ends with dual-license model and a wroclove.rb-special pricing offer. Q&A covers conditional DAG jumps, hero deletion/mutation semantics, migrations (gem-generated), YAGNI, historical state (use paper_trail), and scheduling granularity (follows active-job adapter).