anchor.diff:  
   == Overview
   
  -* Lineage
  -* Ownership
  -** Accountability / Attestation
  -* ...
  -
  -
  -== Types of Platforms
  -
  -
  -* _Infrastructure_ platforms, hold or forward the data to the recipient without altering the data content.
  -* _Enrichment_ platforms, which may blend data from several sources before it reaches the recipients
  -* _Multitenancy_ platforms
  +This document looks at how Waltz could be adapted to enhance it's support for _platform_ applications.
  +It looks at how flows are represented, how lineage can be achieved and how attestations are used.
  +
  +== High Level Recommendations
  +
  +* Adopt attestation exclusion mechanism for platform
  +** Obligation for attestation moves to providers of data to platforms
  +* Invest in lineage interop with external tooling
  +** Enhance flow diagrams / waltz support for 'first pass' lineage
  +* Altering flow representation (i.e. 'via' attributes will complicate solution for little incremental value)
   
   <<<
   
  
positive.code: 
      lf1 -> pf1;
  
      pf1 -> app2 [label="ultimate recipient"];
  
      {rank = same; app1; plat; lf1}
  }
  
negative.code: ----
  digraph B {
  
      plat[label="Platform\n:(", color="orange"];
      app1[label="App1", color="green"];
      app2[label="App2", color="green"];
      app3[label="App3", color="green"];
  