Concept in Krzywda's layered DDD: read models are persisted views (often a single Active Record table) that subscribe to events from one or more domains and shape data for a specific application consumer — e.g. an all-products list in admin, an available-products list on the public site, a ledger, all-orders, monthly financial reports, or sales-team views. Living in the application layer, they commonly combine events from different namespaces. The talk introduces a small DSL that declares, per event attribute, which column to write. Read models should be denormalised and decoupled from one another: depending one read model on another is a common but avoidable mistake. They pair naturally with Hotwire: broadcasts ride on their underlying Active Record callbacks, so small page boxes re-render without React.