More flexibility for modeling state transitions

[socadk]

Context: Aggregate state changes caused by service/entity operations.

While write [S1-> S2x S3] and write [S2,S3-> S4] work I cannot model something like:

write [S1->S2,  S1->S3,  S2->S4, S3->S4]

My workaround is to model one operation per state transition, but the system that I model has a single updateStatus() interface that can cause arbitrary transitions.