Thanks again for taking the time to do this Tiberius. I've loosely followed your work since I've followed @mbauwens as he has so often referenced Sensorcia. So you taking the time to write about this report and the one for @YourOwnAI means so much to me. For our different paths to get to this time, I'm really glad to connect with someone like yourself who I have far more in alignment with than not. Which, in this day and age, is a win in itself. For the most part, I see that most of what's in your report is either in place or is planned in some shape of manner. That being said, there's still plenty in it that I've taken on board to think about. I'd imagine if our roles were reversed, I'd be asking similar questions. So I'll answer a few of the big pieces I thought came out of this report and then if there's anything else you'd like to ask as a follow up now or in the future, please do so. Lock-in is something you mentioned and it's something I have designed the Flowsta SDK and services around, making sure there is no lock-in. Everything Flowsta provides to developers (the SDK packages and the agent-linking zome) is MIT-licensed, so a developer can modify it, remove it or replace it with their own code at any time. With the Holochain CAL then data is never locked in. The Holochain backup data in Vault holds the Holochain keys. The persons whose data it is can take it or recreate it anywhere they like. Building a Holochain app to use the Flowsta SDK changes one main assumption: the person is not their agent key. A Flowsta identity is linked to the app's agent keys by a signed attestation that anyone on the app's network can verify, so one person can have several agents: one per device, all on the same private network, and one per identity when several Flowsta identities share a computer. The app therefore recognises people by their Flowsta identity, keeps each identity's data separate, lists shared records at a fixed address so every device sees the same set, and treats edits and deletions as new records that any of the person's devices can write. Keys, backups and recovery stay in the person's Flowsta Vault rather than in the app, and the app handles the Vault being absent, locked or holding a different identity. None of this ties an app to Flowsta. These are ordinary Holochain patterns, and as I said, the SDK and linking zome are MIT-licensed, so an app built this way still works without them. The developer would then provide their own sign-in, a way to share the network between devices, and backups. Regarding the Cooperative side of things. This is in my DNA. I can't promise how it will or won't look in the end. As I've mentioned before, I was the driving force behind building a Cooperative around a previous startup. shareable.net/interviewed-ma… I made the mistake of putting a crazy amount of effort into creating the Cooperative before there was a business. I'm not going to make that mistake again. The upcoming groups and agreements functionality that I'm building now is a big part of how the Cooperative will run. I'm building the tech I see as necessary to run any group, but in this case, a Cooperative. Holochain DNAs are actually key to this. @hubermanlab talks about overt and covert contracts. Overt being transparent and explicit, whilst covert being much of what we see in orgs everywhere right now. Bringing everything into the overt is what we're building. So as the tech moats disappear, it all becomes about whether the people in any group agree to the overt contracts, and if they don't, they move on based on the agreements they've agreed to. ie, who is responsible for what roles, what happens to data created as part of that group when someone leaves, or how revenue is shared, is all clear. So this world is radically different to what we've known before. But the elephant in the room is that we're no longer just talking about humans. I know this is beyond the scope of your report, but this piece is why I am working with such a sense of urgency right now. I read @harari_yuval's book Nexus at the start of the year when I was in the early stages of designing what I'm building now. It's a pretty long book, so it's hard to summarise, but there is an existential risk that Harari speaks to so well. The risk is around treating Humans and AIs as the same, and I'm not pointing towards a hierarchy, but realising the strengths and weaknesses of each and designing systems around that. AIs are excellent with overt contracts, like what groups governed by Holochain DNAs make possible. Just saying this to paint the picture of what I'm so focused on building right now. So I'm not exactly sure how the OVN patterns or other patterns from other projects map onto what we're building. I imagine it will help accelerate many projects. I highly recommend sending an AI over to the Flowsta SDK github.com/WeAreFlowsta/flow… to ask what potential apps and the people using those apps can gain from it. That's pretty great now, but will be even more so in the next few weeks as the agreements and groups functionality rolls out. I