Apian Peer Architecture Explainer

[jimkberry]

This is the overview Issue for it

• Move Apian Architecture explainer to start-here. #7 Move Architecture splainer to Start-here
• Redo the introduction to the Apian component and Apian messages (see comments below)
• Fix the cloud/apian "callout" thing and end up with just a dotted line
• Put other peers around the cloud
• Show a user action propagating to the cloud and back and moving planes.
• Show a remote action doing all that... AND making an observation happen

[jimkberry]

• An Apian Inst is paired with a local AppCore ****** Put this before the "defines messages" part. (get rid of the "yes... implies..." part)
  (show Apian box)
  Important thing is that it's really a proxy
  ..for the collective *** get rid of "collective" name. Just call it Aggregate when it's needed
  (show cloud/collective) *** move cloud up
  ...with other peers
  (show other peers)

[jimkberry]

The Apian message stuff needs to start by saying that Apian message are mutable wrappers around application-domain directives/messages, then describe the types.

Then : Apian has N tasks:
Distribute incoming Apian messages to other Peer's apian instances.
Decide (as a group) whether to upgrade Reqs amd Obs to CMds.
Distribute CMds to local AppCores
Store CMD log
Chain?
Trie?
on-the-fly Proofs?