Joint position from the panel (both teams agree): ORMs used to host business logic fuse concepts together with no boundaries, like a worm where kidneys, heart and lungs are indistinguishable goo — so you can't transplant anything. Rails' Active Record is the canonical case, but ROM — often positioned as 'better Active Record' — inherits the same failure mode because it still tries to implement business logic through an ORM. All that 'partitioning/boundary' work DDD worries about is essentially cleaning up after ORM-driven modeling.