I had this idea of different write models being used in different bounded contexts, but both being the same aggregate instance (the same events).
For example consider a User aggregate that is used in Administration and User contexts (that is the admin and the user-interface parts of the application). And the domain model says that the user (in User context) cannot do any action on itself (change email, change password, change address, whatever) unless he is logged in (which is the only action he is permitted to do if hes not logged in).
In administration context, however, the action does not need that user to be logged in (basically, an admin can change user's details on his behalf).
Can this be modeled with Event Sourcing as a single aggregate instance (same ID), but depending on the context a different object model would be built from the events? i.e. in admin context, the model does not verify the user is logged in, but in user context, the model does. This way the events would be shared between the contexts.
Is this a good idea? I can smell some issues but I am not completely sure.