Mechanism the talk uses to let decoupled domains cooperate. A process captures a business checklist ('whenever A and B and C happens, do X') at the technical level by subscribing to events and, when triggered, emitting commands on other domains. Example: 'whenever a product is renamed, issue a SetProductNameDisplayedOnInvoice command to invoicing'; 'whenever an item is added to a basket, add it to the shipment picking list'. Processes live between the application and domain layers because they encode project-specific rules. They introduce some data duplication between domains but preserve clean business-logic separation and make it obvious where to change a rule when the business changes it. A simulated e-commerce project already has 25–30 such processes.