Another way to look at this that’s always been clearer for me is “A class (or entity) should have one REASON to change”. Your higher order classes might indeed have more than one ‘thing’ but if those things all have a reason to change, e.g. finance changed its billing processes, then they can live together… This principle is often misunderstood as 'do one thing’.. which causes confusion