User Flow flowchart Orders-->|select_order|OrderDetail Home-->CurrentOrder?{Is there a current order?} CurrentOrder?-->|yes|OrderDetail CurrentOrder?-->|no|Admin?{Is the user an admin?} Admin?-->|yes|CreateOrder Admin?-->|no|NothingToDo!Enjoy/ProductsExplorers Home-->|tab|PastOrders

Requirements All code needs to be source-available OpenSource licences Copyleft (GPL):Allows anyone to reuse and resell PROVIDED that they also use GPL in their software Basically disallows it being used in proprietary software Permissive (apache): Allows anyone to do anything with it

Any place you see "holochain" here, we are refferring to the holochain binary, which is the main code written in rust that does most of the job in networking, data structure and data integrity. Binaries lair-keystore: generate and manages private/public keys pairs. holochain: core platform that runs holochain applicationsExposes two endpoints: ports to connect through WebSocketAdmin Interface: to install and manage happs. Not accessible from the app's code, just from the launcher's admin UI or CLIInstall App Uninstall App App Interface: call functions defined in happ. Accessible from the app's code or any JS CallZome

As any user, I should be able to create a call As any user, I should be able to see all calls // FOR NOW MAYBE CHANGE As any user, I should be able to respond the call If all call slots have been answered, automatically create the promise As any user, I should be able to see all the promises I made As any participant in the promise, I can create a fulfillment reflection on it pub struct Need {

User stories As a member in the network, I should be able to create new inquiries Properties of an inquiry Prompt List of questions -> quantitative indexing As a member in the network, I should be able to see a list of all creates inquiries

Context Internal team moving really fast since they are in feature development mode Friction between internal membrane and karsa In the next months, a bunch of small experiments of real usage of Holochain with the Launcher are going to be started. Next steps? How

Motivating stories Rabble: Nothing new in website repo, READMEs don't work feels therefore like "vaporware" Jack

Goals Launcher binary is attached to holochain releases on github ideally: release of launcher happens automatically Challenges launcher package includes multiple holochain versions launcher depends on the rust holochain client, which also needs to be upgraded to a new holochain version

Resource manager: the one that accepts or declines booking requests. Resouce user: the one that requests to use a resource User Stories The resource manager should be able to create a bookable resource The resource manager should be able to create bookable slots for their resources from this time to this time

Functions map accept_countersigning_preflight_request -> lock_chain SessionInfo -> Timeout and agents to sign PreflightRequest -> entry+session_info PreflightResponse -> PreflightRequest+Signature Bob accepts sequenceDiagram

Encryption and signatures: basic signing and encryption using public/private keys. Bridge calls: call from one DNA to another DNA inside the same conductor. Call remote: call from one agent to another agent inside the same DNA. Countersignature: easy way to create a countersigned entry with multiple parties. Scheduling: schedule a function execution in the future.

A DNA to include into "We", and other apps. You can think of it as the child between RoamResearch and crates.io. Grammar Notebook: a bundle of notes that are structured together in a tree (think of a note with subnotes in it). Bookmarks: every notebook will expose a set of "bookmarks" for other notebooks to reference. Reference: from a notebook, you can reference a bookmark defined in another notebook. Fork: anyone can fork notebooks in a shared space, and do PRs to them.

Challenge Show what we are going to code in playground devcamp8 Q&A Code Break

Creating a group coherence with holochain apps Context A key component of group coherence, is that the members of the group know the "rules of the games" that they are playing together. Since every Holochain DNA is fundamentally a "rules of a game", we can create a powerful group coherence tool by making it easy to compose DNAs and their UIs inside of a membrane of people. We is a DNA and UI that provides this functionality, along with a pattern on how to declare and share functionality across the sub-DNAs that are composed into the group. Zomes membrane zome We have to have a way to determine who gets to join the group. In this design we delegate that to membrane zome, assuming that there will be different ways to do this. Some initial options: 1. no checked membrane, just assume players in the group know the UUID which serves as a sort of secret. 2. membrane-proof check against an agentPubKey stored as a DNA property to check if they have signed a membrane proof

DNA del Mercado Membrana: invitación por parte de la asociación: mayoristas y minoristas La asociación asigna roles de mayorista. Las transacciones son privadas y encriptadas. Mecanismo de witness eager o lazy, a definir También pueden ser los mayoristas los que publiquen la transacción firmada por el minorista. sequenceDiagram

Reputation data ELO Rating system DataType: struct GameResult { timestamp: Timestamp, winner_index: u8, // index of the winner inside the participants array participants: Vec<AgentPubKey>, num_of_moves: usize

Guillem: AWS instance (free tier) URL: kitsune-proxy://t9471bRVOKH-HMInwG5jqwk3KBiiSmiEhy6F5Cu_8ys/kitsune-quic/h/52.14.147.62/p/22224/-- Holochain Commit Hash: 785061ba232ff98ceb13fc245f7f2a62d3ecb582 Holo: Digital Ocean community proxy Type: tx2 proxy URL: kitsune-proxy://SYVd4CF3BdJ4DS7KwLLgeU3_DbHoZ34Y-qroZ79DOs8/kitsune-quic/h/165.22.32.11/p/5779/-- Holochain Commit Hash: a6ac0439670ba367c723a80d3b8bc7c419aa5f6e (Apr. 23, 2021)

DNAs PictureConversation DNA Zomes picture_conversation Entries Links Anchors

#6 Real Time Collaboration So! Finally we've built some amazing small community in our village. People are engaging, tagging things, exchanging with mutual-credit, and it's awesome. Now people want to have some more advanced collaboration tools, that can work real-time. One major need is real-time collaborative edition of documents, eg hackmd. Challenges: How can you handle real-time interactions with feedback as immediate as possible in a fundamentally eventual consistent DHT? What trade-offs can you see around scaling the collaborator agents, and how are you taking those into account?