anchor.diff:  
   .Example query 2:
   
  -Given a database containing two nodes, and the following query,
  -the sequence below describes a non-obvious query execution.
  +Given a database containing two nodes, and the following query, the sequence below describes a non-obvious query execution.
   
   [source,cypher]
   ----
  
positive.code: RETURN x as column
  ----
  
  
  === Benefits to this proposal
  Explicit state change visibility makes it possible to understand queries without having to worry about ordering of updates and reads.
  
  From an implementation perspective, these semantics also allow us to make some queries more performant than they can be today, by ignoring statement state for a lot of graph reading, and saving us from eagerly producing matching results before updates can be applied.
  
negative.code: This replaces the past definition in CIP20140109.
  
  === Caveats to this proposal
  
  None known at the moment.
  