TrustGraph Rollup

[harlantwood]

Background Context

A TrustGraph is

• initiated from a collection of TAs - generally to people or orgs in order to follow their webs of trust
• [someone] rolls up the network into top level TAs for that TG (ongoing)

A TrustGraph:

• public viewable or private viewable
• private viewing is by invite code/cap tokent
• has an underlying DHT
  • or two: 1 for read, one for write ? Or use validations/cap tokens for these?

Rollups

• an agent could only roll up what is visible to them
• trust atoms that are an amalgam value for each target / content combination
  • maybe extra store full original TA list?

Code Sketch

// within new hc_zome_trust_graph:

pub fn create_rollup_atoms()

eg : given my TAs:

me -[holochain, 0.99]-> zippy
me -[holochain, 0.80]-> robert
me -[holochain, 0.99]-> HIA
me -[engineering, 0.88]-> Telos

zippy -[holochain, 0.99]-> HIA
robert -[holochain, -0.99]-> HIA

robert -[engineering, 0.99]-> Ethereum

then rollup atoms will be:
me -[rollup, holochain, 0.98]-> HIA                  // actual value is TBD
me -[rollup, engineering, 0.99]-> Ethereum     // actual value is TBD
me -[rollup, engineering, 0.88]-> Telos            // actual value is TBD

possibly with addl metadata in the `extra` containing the source TAs (zippy & robert)

• Add new chunk to TA link tag: type -- before content
• Set type to rollup for rollup TAs
• Otherwise type is empty