introduce Reactor::ResourceActionable

as a way to DRY up controller action_event declarations
while also enforcing a nice naming convention for your activity model.

Consider the benefits of a event data model DSL that is a superset of the database model DSL.
And in an even more cooler world, the data model naming will match the business logic naming.
And thus we have significant potential for parity between our business, database, and event DSL.