wroclove.rb 2025 lightning talk on implementing process managers in Ruby at the code level (which Mat called 'automation' in his talk). Explains process managers as a business-process implementation orchestrating departments — at the technical level a mapping from events to commands. Uses a reservation process example with three input events (pricing offer accepted, order confirmed, order cancelled), a state with three values, and five possible output commands (reserve, reject, accept, release stock, dispatch stock). Walks through the five parts of a process manager in code: (1) subscribe to events; (2) build state from events using a data object with status and order lines; (3) decide what to do based on state; (4) return commands; (5) pass commands to the command bus. Highlights reserve_stock as the non-trivial case where all order-lines must succeed transactionally — otherwise the code reverts everything. Shares helper-methods infrastructure that takes an event store and a command bus. Code is taken from the RailsEventStore/ecommerce reference repository, specifically the reservation process file.