Theory:
1. Expose use-cases (context) as first-class citizens of your code.
2. Each use-case selects which objects are needed for this use-case.
3. Extend the objects only with the roles that are needed in this use-case.
4. Start the interaction.
Example:
Buying a product.
1. UserBuysAProduct object, that can be executed.
2. Objects/actors needed: user, shop
3. Extend user with a Buyer role and shop with ProductCatalogue and OrderManager.
4. call shop.buy_product(user, product)
The rationale is, presumably, that you can add and change particular use cases independently of each other and the core model.
Right?
The idea is that the Data doesn't change that often, so it's kept separate from the things that change frequently - roles, use-cases.
Exposing use-cases is also an important goal, usually they are scattered across the codebase.