I've designed something like this before but in the context of orchestration. A 'read' implicitly became a subscription in the meta-process and any subsequent changes to the consumed value triggered updates to the consumer process that were either explicitly caught or handled through an implicit context process.

This allowed process definitions to remain simple enough for business analysts to comprehend while still able to cover real world complexity.