interested:Tomis Eric Nico Dora Discussion: Timing Make a formal announcement of Coasys and SAFT sale by end of next sprint (July 15) What's needed?

1. Full AD4M Node on HP Not gonna happen now / huge interest to make happen after Holo beta is out Could run in a Docker-container We would need to attach AD4M to the Holo key/signing wormhole 2. Only Holochain gets sourced-out to HP user still runs an AD4M-executor, which remote-controlls the Holochain instance run on the HP Insight: AD4M user can show up as app publisher in holo

digraph { 0 [ label = "0" ] 1 [ label = "1" ] 2 [ label = "2" ] 3 [ label = "3" ] 4 [ label = "4" ] 5 [ label = "5" ] 6 [ label = "6" ] 7 [ label = "7" ] 8 [ label = "8" ]

A DM (agent-to-agent) implementation exists in AD4M since fall 2021. While there are tests for this in our CI, we have no UI. It is both specced out in an interoperable way as DirectMessage Language, and we also have an implementation for this interface, based on Holochain. This Holochain implementation uses p2p signals if the receiving agent is online, and posts an encrypted entry to the DHT if not. AD4M Direct Messages are conceptually linked with AD4M Friends, since adding someone as a friend, makes the Executor install the other agents DM Language, which in the case of our Holochain implementation means: friends show up as relays for Direct Messages, if the receiving agent is offline at the time of sending. Possible UI implementations 1. Adding a new DM UI component to Flux

digraph { 0 [ label = "0" ] 1 [ label = "1" ] 2 [ label = "2" ] 3 [ label = "3" ] 4 [ label = "4" ] 5 [ label = "5" ] 6 [ label = "6" ] 7 [ label = "7" ] 8 [ label = "8" ]