Fourth anti-pattern in Ladd's talk. A class that mixes entity business logic, command handling, and event projection into one object for convenience. The entity stops being recognisable as the domain model, and the big testability win of event sourcing (isolated entity tests, isolated projection tests, handler tests asserting on what was written) is forfeited. Ladd attributes its popularity to web developers being uncomfortable with object-oriented structural design (preferring to subclass a framework artifact and dump code in) and to the 'we'll refactor once we know the boundaries' rationalisation — backwards reasoning, since coding is what happens after engineering, not the way you learn what the system should be.