Volatile fields

[JonathanMace]

Volatile fields are fields that we only want one side of a branch to ever see.

When we branch a context, only one side of the branch will get the field; the other side will get null.

Volatile fields enable the implementation of state-based CRDTs based on vector clocks that have random component IDs; you declare a component id field that is volatile, and a map<id, ...> for the values.

Volatile fields are always transient, because we can't guarantee an intermediary component will respect the volatile-ness