The condition plugin system is useful on its own, but a user interface to allow for groupings of conditions to be made for generic reuse purposes helps promote the basic needs of both a page management style solution as well as a Rules style paradigm. This UI is incomplete but is basically working at this point and allows condition plugins to be configured and that configuration to be saved into a Condition Group config entity. The entities themselves cannot yet execute the configured conditions within them, but the UI is working if you inspect the entity as it is generated. This issue depends upon 4 other patches right now.
The modal is saving the condition configuration into the entity appropriately. There is a blank div on the form that needs to be populated with condition summaries (there's a method on conditions to do this for you).
A user interface for TypedData probably needs to be build to tell the condition group what sorts of contexts will be required in order to fulfill this grouping of conditions. This is incredibly non-trivial and I will be filing a follow up for it shortly.
Configuration of the conditions will need to inspect what typed data is available and allow the configurer of the condition to select which (relevant and available) context to use in order to fulfill the condition.
Once the entity type is saving what TypedData conditions it requires to operate, it will need methods exposed on it to satisfy these contexts and pass them to the conditions appropriately for execution.