anchor.diff:   these trees may have more relaxed placement rules.
    . creation of composite (uber) trees made from multiple sub trees, such as accepted taxonomic trees from multiple shards
   
  +WARNING: We should take a closer look at the needs of List compilers and Tree composers to see if the difference in the
  + set or requirements leads to different solutions for each.
  +
   ==== Editors
   
   Based on the above use cases, and current editor usage, it looks like we need two different editing pathways for trees.
  
positive.code: Perhaps the second, compositional, editor is logically broken into an uber tree manager and a checklist editor.
  
  ==== Search
  
  ===== use cases
  
  
negative.code: 
  You can even display the synonyms without further query.
  
  NOTE: Greg W says to make the search useful we'll need to store the type of synonym as well. This could be stored
  in a jsonb field so we retain the speed of the trigram indexed synonyms search with the ability to filter on instance type.
  
  === Profile data
  
  The Profile data will be stored as a JSON object/document field in the tree_element. This allows arbitrary extension of the
  