Nice and also from my experience - usual state, usual decision.
If I'll be the decision maker (instead of the 'only developer') I would always prefer solution with one implementation. Another words - create solution with all entities CRUD stuff, then deploy it 3 times with different 'Menu.config' (hiding or displaying
what is relevant and what is not)
But because we very often met decision makers from the business side, usual solution is more rigid: 1) create the first one 2) make a branch 3) changes to both implementation? do it twice (or play with merging tools in TFS :)
So, I prefer one implementation, but the reality (until now) never allows that.
The Catharsis framework is more business-domain oriented, then based on modul-puzzling. So if you in one solution create complete layers (data, busines, UI) for one entity - it is hard to move it to another one.
Not as great answer as it could be, I know ... :)
Enjoy decisions with business guys ...