SOCIAL LEDGER 2�THE NEXT GENERATION
T H E S O C I A L L E D G E R I S O U T T H E R E
Photo: Joachim Stroh, Twin Peaks, SLC
PROLOGUE
Thank you for coming with us on this journey. It won’t be an easy road ahead. The conversations won’t be gentle at times. But, if we keep together as a team, we can go against the dying of the light*. It looks good for our trajectory.
To sign up for this trip, please visit the Social Ledger Lab and type
/dig actions
Locate Social Ledger 2 Design Specs and click on a commitment level.
Let’s co-create SL2!
The purpose of this document is to record our co-design and co-creation process for the next generation of the Social Ledger and anyone who is interested can participate in this process. �Here’s a rough outline of the design path:
How we do this
Here’s how we can conceive and implement SL2:
Why we do this
Where we came from
OVERVIEW
“The Social Ledger is cooperation on a meta-data level.”
—Jim Whitescarver
Affordance
Structure
Scaffold
Foghorn
Bridge
The Social Ledger has three distinct levels.
Level 1�Organization
Any organization that supports open info & knowledge flows can use the Social Ledger.
Open Source Projects
Local Communities Makerspaces
Cooperatives
WHO & WHERE
Level 2�Team
The Social Ledger provides the right amount of scaffolding to assemble teams and to structure your organization.
Where? Who?
Location ID
Channel Name�Circle Role
Level 3�Activity
The Social Ledger records various activities performed on social objects by individuals being part of a team.
Documents & Decks
Ideas & Proposals
Decisions & Milestones
Organization
ACTION
User Interface
Although the Social Ledger has a variety of user interfaces, the primary interface for SL2 is the card.
At a minimum, each card has a title, an image and an action button which changes in accordance with the state of the card.
Any action that is part of an interaction is recorded in a (social) ledger, any action that is part of a transaction is recorded in a (financial) ledger.
The Activity
Jane
Joe
Joe
The Collective
JOIN
ACCEPT
The Team
JOIN
ACCEPT
COMMIT
ACCEPT
All Three Levels
Taken together, the Social Ledger glues the collective, the team and the activities together into a single coherent & distributed system.
Identity
Organization
CREATE
CREATE
Entry Points
There are three entry points into the Social Ledger:
Each card has its own provider - the card itself is merely a shell (frontend) to the services provided.
Wallet
CREATE
Provider
Provider
Provider
Identity
Organization
ADD
CREATE
Example Path (aka Generative Sequence)
As new cards are added to the system (at a specific location), they become immediately visible & actionable (aka stateful) to other team members.
Wallet
ATTACH
Norms & Protocols
SET
Video & Text Chat
HOST
...
Loomio Service
Identity
Wallet
CREATE
CREATE
Your Wallet
There’s a special card that represents your wallet. You use it to interface with a financial ledger and to pay for services or to receive rewards for activities.
Provider
REQUEST -200
Spimes
"The future will see a new kind of object that will be sustainable, enhanceable, and uniquely identifiable. Sterling coins the term “spime” for them, these future manufactured objects with informational support so extensive and rich that they are regarded as material instantiations of an immaterial system. Spimes are designed on screens, fabricated by digital means, and precisely tracked through space and time. They are made of substances that can be folded back into the production stream of future spimes, challenging all of us to become involved in their production." -Bruce Sterling
A complete set of cards can be seen as a (virtual) box of spimes that contains all necessary elements to build a great organization from scratch.
Note Taker
Decision Maker
Transaction
CREATE
Video Conference
ADD -100
Starter Set
This is a proposed starter set for any new organization joining the Social Ledger.
Identity
CREATE
ADD -100
ADD -100
Chat
ADD -100
Card
ADD -100
Card
ADD -100
Tutorial
20-min knitting session
Meditation�
2-min session
What else?
Can you come up with new ideas for cards (spimes)?
Anything goes from applied to abstract, from tool-based to mind-based.
Give it a title, an icon, and a default action (later specs will require more details).
BEGIN
Your Card
?
Peer-to-Peer Call�
Jim Brewer
CALL
WATCH
Ownership
The Social Ledger raises some interesting questions on ownership over you personal data and data you have shared with others.
A design principle here is to “own” certain cards in the system and the right to erase all data for this card (RTBF).
Your Card
?
My Identity�
jim@hotmail.com
ERASE
My Wallet
dfe45-sdfg-34rf-dr4f4
ERASE
My Journal
17eX1MX-h3xLsi_MkAv0hYnIL
ERASE
FRONT END
Card-based Interfaces - 2D
Card-based Interfaces - 2D
Card-based Interfaces - 2D
Card-based Interfaces - 2D
Card-based Interfaces - MetaMaps
Card-based Interfaces - AR
Holonic Interfaces - RR
Different card decks serve different purposes and provide different levels of value, eg. a starter deck helps for onboarding, a business deck helps for strategic modeling, a spiritual deck helps for energizing, etc.
BACK
FRONT
DATA FLOWS
Flow
Auth
Login &�Registration
Cards�Context &
Behavior
OAuth?
LDAP?
Wallet�Payment �& Keys
OpenMoney?
Firebase?
DDB/DHT?
Apps�Content & Functionality
3rd Party
multiple OAuth identifiers or LDAP integration
identity credentials
micro�payments
data�integrations
Social Object as Card - current
Social Object
Data
Tool
LINK
Address (Domain.Channel.Object)
Descriptor (Name, Size , Type)
Metric (Efficacy, Co-efficacy)
Actor (LOC, LOE, Datetime)
Address → Namespace
CRD
Webhook
Social Object as Card - example
Mattermost Post
POST ID
Mattermost
LINK
Address (Domain.Channel.Object)
Descriptor (Name, Size , Type)
Metric (Efficacy, Co-efficacy)
Actor (LOC, LOE, Datetime)
Address → MM Channel
CRD
Social Object as Card - future
Social Object
Data & Behavior
Tool
DO
Address, Descriptor, Metric, Actor
History (e.g. #uses)
Tool (e.g. activity status, last modified)
Protocol (e.g. host, recorder)�Behavior (e.g. invite)
Protocol
Address → Namespace
Protocol → Functions
CRUD
API�SDK
Bot
Plugin
Webhook
Social Object as Card - example
Zoom Session
Zoom Tool
DO
Video Conf Protocol
IN PROGRESS
CRUD
JOIN
Offboarding & Intangible Assets
Tool (e.g. FB, Twitter)
LINK/WEBHOOK
Application Namespace
Corresponding Expedition Space
CONVERSATION CARD
INTANGIBLE ASSET
KNOWLEDGE RECIPE
ROPED PATH
FB Identity
SL Identity
SERVICE ENDPOINT
ACTIONABLE INSIGHT
“If you look at the mathematics of the quantum theory, it describes a movement of just this nature, a movement of waves that unfold and enfold throughout the whole of space. You could therefore say that everything is enfolded in this whole, or even in each part, and that it then unfolds. I call this an implicate order, the enfolded order, and this unfolds into an explicate order. The implicate is the enfolded order. It unfolds into explicate order in which everything is separated.” - David Bohm
Social Object as Card - enfold past
Zoom Session
Meeting Agenda
Zoom Session
Project Plan
Design Document
Project Outline
...
IN PROGRESS
COMPLETED
UPDATED
UPDATED
UPDATED
UPDATED
Mattermost
DISCUSSED
Loomio Decision
DECIDED
Zoom Recording
CREATED
This is similar to adding links to social objects inside a chat but would focus only on the social objects. This could be done by the ledger bot.
Article
BOOKMARKED
ACTION
ACTION
ACTION
ACTION
ACTION
ACTION
ACTION
ACTION
ACTION
ACTION
Social Object as Card - unfold future
Social Object
Social Object
Social Object
Data
The right cards (or deck of cards) played at the right time, in the right sequence and at the right location will generate an emergent outcome, an unfolding of storylines.
Unfolding Future
Social Object as Card - in streams
Domains
Channels
Services
Activity Stream
Conversations
Collectives
Data continuously streams in and out of systems from different locations and at different times. The tesseract is a place where we can aggregate streams and provide a 2D or 3D view on these 4D streams.
“We are the bridge.”
Social Object
GraphQL
3. Books
2. Strings
1. Decks
Data & Behavior
API/SDK/BOT
Space/Time
Maps
Cards
Grids
Pandas
Tasks
Links
Graphs
Docs
Social Object
Apollo/GraphQL
Card Events
API Events
a: true @ t = 1
b: true @ t = 2
c: true @ t = 3
a: true
b: true
c: true
When
Do
x: action
y: action
LAUNCH
Input�(API)
Output�(JSON)
COLLABORATIVE�SENSEMAKING PATTERNS
Chronological Ledger
Sensemaking Pattern
Activism
Social Learning
Book Marking
Social Cognition
Collective�Insights
Action
Action
Action
Action
Action
DATA FEEDS / SOCIAL GRAPH
COLLABORATIVE� & IMMERSIVE STORYTELLING
Mindful�ness
Social�Interaction
...
Enactive�Inter-�subjectivity
Social Presence
Gover�nance
SUB-PATTERNS
COLLABORATIVE�SENSEMAKING PATTERNS
DATA SOURCES &�API INTEGRATIONS
AFFORDANCES� & CARD UI/UX
Social Ledger
COGNITIVE FEEDBACK LOOPS
SCENARIO
Cards as Portals
Outline
Join Collective
Holochain
NOT JOINED
...
NOOMAP
NOT JOINED
DigLife
JOINED
RChain
JOINED
JOIN -1000
JOIN +100
OPEN
OPEN
Open below
Open below
Request below
Request below
0
0
0
0
My Value Indicator
...
...
...
Subutai Hub - Orgs
Service Request
Zoom
NOT INSTALLED
Zoom service has not been activated yet. To activate this service, 1000 tokens will be deducted from your account.
Mattermost
NOT INSTALLED
Google Drive
NOT INSTALLED
Loomio
NOT INSTALLED
REQUEST -1000
REQUEST -100
REQUEST -100
REQUEST +200
Request below
Request below
Request below
Request below
0
0
0
0
My Value Indicator
Mattermost service has not been activated yet. To activate this service, 100 tokens will be deducted from your account.
Google Drive service has not been activated yet. To activate this service, 100 tokens will be deducted from your account.
Loomio service has not been activated yet. If you activate this service, 200 tokens will be added to your account.
Cloudron Store - Apps
Gamestorming (Dave Gray)
Squiggle Bird
NOT PLAYED
...
The Squid
PLAYED
Hero’s Journey
NOT PLAYED
Cost-Benefits
NOT PLAYED
PLAY +100
PLAY AGAIN +100
PLAY +100
PLAY +100
Request below
Request below
Request below
Request below
0
0
0
0
My Value Indicator
...
...
...
Story Sequence - Zoom
Zoom
NOT SCHEDULED
The service has been activated (-1000). A second service for the meeting notes has been linked to this card.
Zoom
IN 4 HOURS
Zoom
IN PROGRESS
Zoom
ENDED
SCHEDULE -300
LAUNCH +100
JOIN +100
VIEW -100
Meeting Agenda
@mwl, @joachim, @gary, @christina
Loomio Decision
Dec 4, 2017 @ 4:15pm ET
Dec 4, 2017 @ 3:00pm ET
Schedule below
-1000
-1300
-1400
-1800
A meeting has been created (-300) resulting in a balance of (-1300). It also displays the value you provide if you participate (+100).
4 people have joined the Zoom session and after you joined the balance is (-1400).
The Zoom session has ended (balance is -1800) and a link to the video recording is provided (-100) to view.
Service Protocol - Zoom
Zoom
NOT SCHEDULED
SCHEDULE -300
Zoom Protocol
Zoom is our video conferencing tool. We are holding regular meetings throughout the week that you can join by clicking on the link below. The first time you join, you will be prompted to download and install some software on your desktop. We aim to record every meeting and share it with all members - should you join a Zoom session and need to record it yourself, please click on the Record Session button below for more info.
Schedule below
-1000
ARCHITECTURE
Dev Stack (local)
Architecture (decentralized)
Appi
Cardi
DB
DB
APIi
Backend
Frontend
UIi
Card-based UI + Firebase DB
Multiple cards can communicate with each other (e.g. card1 interacts with card2.
Multiple services can be invoked for an actor (e.g. a kanban service and a crypto wallet)
Multiple databases can be federated to allow for decentralization.
Each service will have its own (proprietary) database backend, accessible via APIs.
Architecture (decentralized)
Mattermost
/dig command
Social object Actor
Agent
Mattermost webhook
Social ledger
state
APIi
Backend
Frontend
UIi
Mattermost Integration
Social objects are the meta-data container for a set of functions executed in an application.
Patterns of commands on a channel form the local language of social objects.
Events include patterns on a channel, state of a social object/actor/agent, time reached and external event.
Webhooks are a way to maintain a backend connection between the social object and the application.
Card coupling with API calls
Social Object
DB
Application
poll via REST
CRUD via REST
subscribe via HOOK
execute via ACTION
read
relate via UI
write
delete via ACTION
delete via REST
delete via HOOK
delete via READ
delete via WRITE
delete via APP
delete via CARD
1
2
3
4
a
b
c
DELETE
Application
Card
Firebase API
ACTION/LINK
Action
Application API
State
PHP/AXIOS API CALL
UPDATE
CREATE
CHANGED�ADDED
POST WEBHOOK
OTHER CLIENTS
From polling to subscribing
Architecture (distributed)
DAppi
Cardi
Key-Value Store
Backend
Frontend
UIi
Card-based UI + Distributed Ledger
Card Components
Card�Sorter
Card�Dispenser
Card�Vieweri
Card�Controlleri
Card�Modeli
Card�Connectori
Shared modules - organize cards on screen (stack, sort, filter) and add new cards from (free, custom, advanced) decks.
Web Component written in Vue.js containing all four parts.
<template>�<script>
<style>
Card-based UI + Agnostic DB
This is about editing the code directly "on the card", e.g. being able to open the code for the component, edit it on the fly, and save it back to the system, all while running it. So, when you copy a card, the code would be copied (duplicated) as well and you can continue refine the new card.
Card Programming
Component:�Liquid Democracy
Code Editor
A component (e.g. a card) is listed in the view..
.. and edited in an online editor
.. and committed to GitHub
...and hot-deployed to production.
COMMIT
edit
commit
fork
merge�deploy
Component Code
Component State
API
...
owner & contributors
IMPLEMENTATION
2019 Timeline (5th DRAFT)
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
Server Config 1
Card Subsystem
Card 1
Card 2
Card 3
Currency Subsystem
Card 4
Card 5
Card 6
Identity Subsystem
Firestore
RChain (Immutable record & history)
Holochain
Noomap Integr
Metamaps Integr
Specifications 1
Server and App Monitoring & Maintenance 2
Card 7
Card 8
POC Currency
Currency 1
Alt Currency 2
POC Provider
Provider 1
Alt Provider 2
Database Subsystem
Graphics Subsystem
Alt App Config 2 (Sandstorm)
Cloudron Config 1
Alt App Config 3
Alt Server Config 2 (Subutai)
Alt Server Config 3
Specification 3
Specification 4
Specifications 2
Collab Coding Env
Code Testing & Maintenance Protocols 2
Base Camp
D3
Camp 1
Server and App Monitoring & Maintenance 3
Code Testing & Maintenance Protocols 3
Camp 2
Camp 3
Config 1
Architecture Components 1
Social Object
Social Object
Action
JSON DATA
Application
APP DATA
Meta Data�Whatever data is needed
API Data�Whatever data is available
2 Card
1 Card Container
3 Card Logic
6 Data Store
8 App Container
9 App
STORY SPACE
APP SPACE
4 Pattern Logic
5 Real-time Data
7 API Calls
Architecture Components 2
Dev stack [Backend, Orchestration, Frontend]
Subutai [App Mgt / OAuth / SSO]
Cloudron [App Mgt / OAuth / SSO]
App
API
….
Social Ledger
...
...
Submit app to Cloudron Store
Wallabag
Matter
most
KanBan
Meemo
Ship it!
Build it!
Web UI
Mobile UI
Orchestration & Logic
Micro�Service
API
...
DB �API
Ember
React
Vue
Voice UI
Architecture Components 3
Cards�DOM (2D)�Three.js (3D)
Graphs�D3.js
Other UIs�Webhooks
Voice Services�VR/AR
Meta Data�API
Mattermost�API
Zoom�API
AI/Bot�API
Facebook�API
Currency
API
JSON DATA
DATA SCHEMAS/MODELS
DATA RESOLVERS�DATA MEMOIZATION
RESTful DATA
DATA QUERIES� IN-PLACE EDITS�DATA MUTATIONS�DATA SUBSCRIPTIONS
CONTAINER �SELF-HOSTED, AWS, GCP, SUBUTAI
FRONTEND�EMBER, REACT, NEXT, VUE
LOGIC LAYER - WHEN…. DO….
BACKEND�GRAPHCOOL CLI and IDE
Identity
API
100
1014�(beyond trillions)
100
100
100
100
100
100
SCHEMA STICHING
Architecture Components 3
Cards�DOM (2D)�Three.js (3D)
Graphs�D3.js
Other UIs�Webhooks
Voice Services�VR/AR
Meta Data�API
Mattermost�API
Zoom�API
AI/Bot�API
Facebook�API
Currency
API
Identity
API
100
1014�(beyond trillions)
100
100
100
100
100
100
“At present there is no existing science whose special interest is the combining of pieces of information. But I shall argue that the evolutionary process must depend upon such double increments of information. Every evolutionary step is an addition of information to an already existing system. Because this is so, the combinations, harmonies, and discords between successive pieces and layers of information will present many problems of survival and determine many directions of change.”
Gregory Bateson, Mind & Nature, 1979
Architecture Components 4
WHEN <context> AND <conversation> AND <content> AND <entity> AND <like> AND <price> AND <presence>
DO … ACTION <add card> <notify user> <link upstream> <begin session> <commence sequence>
Meta Data�API�noSQL/RDBMS/Neo4j�Holo/R/Blockchain
MM API
Conversations
Zoom API�Calls
FB API
Currency API
Wallet�OpenMoney
Identity API
Auth0�Sovrin
100
1014�(beyond trillions)
100
100
100
100
100
100
DATA LAYER
ORCHESTRATION LAYER (VIA RESOLVERS, SCHEMAS/MODELS & CONNECTORS)
Cards�DOM (2D)�Three.js (3D)
Graphs�D3.js
Webhooks�Mattermost
PRESENTATION LAYER
“How do I get the data for Authors?” and “Which backend do I need to call with what arguments to get the data for Posts?” -source
“What actions in this context, can be enabled on this card?”
Voice
Services
Alexa
VR/AR
VTime
GraphQL
ANYONE CAN CREATE..
ANYONE CAN ADD..
SL QL
UI
UI
UI
UI
API
API
API
API
Architecture Components 5
type Card {
id: ID!
title: String
type: String
actions: {
name : String
link: String
points: Int
}
}
type Query { }
type Subscription { }
type Mutation { }
type Query {
cardsBySpace(spaceID: String!, limit: Int!): [Card]
}
type Query {
cardsBySpace(spaceID, context) {
context.mysql.raw(
'SELECT * FROM spaces WHERE spaceId = ?',
spaceId,
);
}
type Query {
cardsBySpace(spaceID
return context.mongo.collection('spaces’).find({spaceID});
}
MVP 1
View Cards
Add Card,�Create Space�Organization:Domain:Channel:Project
Presence, �P2P Chat
Remove Card,�Open Card
Document
Conference
Chat
Bookmark
Door
Door
Space
Space
Space
Space
Organization→Domain→Channel→Project
Card Container
Use Case: Sudo Power Card
Newsletter
OPEN
Users with This Power
Scope of This Power
Steve Taylor (active since 2/5/2017)
Michael Linton (revoked since 3/4/2018)
Jim Whitescarver (active since 3/6/2018)
Gary Coulter (active since 3/8/2018)
Marketing / Newsletters
Add User
Add Subdomain
Do’s and Don’ts of This Marketing Power
Do
Don’t
Meta�Data
Mail�Train
Sudo Power
CLAIM
Marketing
Use Case: Liquid Democracy
“Delegative Democracy, or liquid democracy, lies between direct and representative democracy. In direct democracy, participants must vote personally on all issues, while in representative democracy participants vote for representatives once in certain election cycles. Meanwhile, liquid democracy does not depend on representatives but rather on a weighted and transitory delegation of votes. Delegative democracy through elections should empower individuals to become sole interpreters of the interests of the nation. It allows for citizens to directly vote on policy issues, delegate their votes on one or multiple policy areas to delegates of their choosing, delegate votes someone else delegated to them to another voter, or get rid of their votes’ delegations whenever they please.” -Wikipedia
emergent structure
Use Case: Liquid Democracy
Voting Screen - Regular or Meta Vote
CLAIM
Issues
Issue #774
Tags: Marketing
...
Issues
Issue #774
Tags: Marketing, Finance
...
Issues
Issue #774
Tags: Technology
...
or
or
Claim or create an issue. You cannot vote on an issue that has not been claimed. Tags can be used to filter an issue or domain. Issues can have multiple tags.
Vote on an issue. Vote button only visible if issue has been claimed; you cannot vote on an issue that you own. Buttons are only visible if you or your delegate have not voted yet (delayed vote).
A vote is recorded in the ledger and can be undone or changed before the deadline. An iterative vote can be added to assure follow-ups on sub-issues that arise. Are you allowed to undo you or your delegates vote? PRELIM: YES
You or your delegate voted on this issue on 6/11/18 @ 4:00
Issues
Issue #774
Tags: Operations
...
or
A vote on an issue is time bound and archived accordingly. A quorum can be added to reach min participation rates (along with a no-op vote). The number of empty avatars denotes the number of required votes (e.g. 3). Should a real-time tally be displayed or counting votes at the end? Both?
This issue has been closed�on 6/11/18 @ 4:00
↑ UP
↓ DWN
⟳ NO
UNDO?
Issues (ballots, policies, bills, proposals) reside in their own tracking system and data is fetched via API calls.
REOPEN?
Use Case: Liquid Democracy
Identity Screen - Delegation or Membership
Dorothy�Voting Power: 3 votes�Tags: Marketing, Operations
UNDO
Beatrice�Voting Power: 186 votes�Tags: Technology
Charlie
Tags: Governance, Finance
Anton�Voting Power: 99 votes�Tags: Marketing, Finance, Mission
DELEGATE
Delegate your vote to another candidate. Sorted by number of votes or other criteria (e.g. random) . Tags can be used to match an issue or team or domain (e.g Marketing).
Click on a profile to learn more about a candidate. Every active member can be represented here given that they have chosen one or more tags.
Only candidates that are eligible to vote for listed domains can vote. There’s a voting process to add people to domains.
A delegation is recorded in the ledger and can be undone or changed at any time; at any time you can withdraw your delegation.
You delegated voting rights� to Jill on 6/11/18 @ 4:00
"The Golden Rule of Liquid Democracy:
If I give you my vote, I can see what you do with it.” (min. transparency)
and ��“Represent at least one category” (min participation)
...
...
...
The bottom row shows delegators (aka supporters, members who delegated their vote to this person). Can be direct or transitive, but must match the tag for the entire delegation path, hence full delegation.
Click on the verified votes to see a record of all votes. Only candidates that are (a) eligible to vote and (b) comply to a DAG (Directed Acyclic Graph) are listed here.
Gain extra voting power (or simply be featured) through expertise levels, matching wins, participation rate, etc.
Beatrice is an elected trustee for Technology until 10/11/19
↑ UP
↓ DWN
⟳ NO
Use Case: Liquid Democracy
Emergent decision through Individuals, Unmanagers, and Trustees
Trustees (100+ votes, trustworthy)
Unmanagers (2-99 votes, stable)
Individuals (1 vote, variable)
Supertrustees (1000+ votes, trusted)
Use Case: Liquid Democracy
Second Order Cybernetics (Meta Vote)
MISSION CIRCLE
First Order�Decision Making�A regular vote on the issue.
Second Order�Mission Alignment
A meta vote on the issue.�Degree of alignment denotes a quorum, suspension or elimination for issues that seem misaligned.
PARENT CIRCLE
Use Case: Liquid Democracy
Implementation
Joe’s�Campaigns
Joe’s�Protocols
Joe’s�Protocols
Add
Joe’s�Posts
Joe’s�Collections
Joe’s�Spaces
Joe’s�Feeds
Joe’s�Convos
Stitching Protocol Draft
Shared Space (Context: Project AI)
Personal Space (Context: Joe, all cards)
Joe’s�Identity
Jane’s�Identity
Service Provider
Joe’s�Card
John’s�Identity
Joe’s�Spaces
Joe’s�Collection�#AI
Joe’s�Identity
Joe’s�Mattermost�#AI
Joe’s�Collections
Joe’s�Feeds
Stitch
Joe’s�Wallet
Joe’s�AI Bots
Joe’s�Convos
Ask
Ask
Ask
Edit
Open
Accept
“The cards Joe plays”
Play
Play
Play
Auth0
Auth0
Auth0
Auth0
“What Joe is capable of doing”
“The rewards Joe gets”
John’s�Collection
#AI
Copy
View
Action
Add
Add
Open
Tame
Open
John’s�Telegram�#ML
View
Add
Joe’s�RSS Feeds
#AI
View
Gary’s�Bot
Run
Joe’s�Posts
Write
Joe’s�Posts�#AI
Read
4
1
6
2
7
1
“The data Joe owns”
Jane’s�Discord�#AI
View
8
Joe’s�Protocols�#Sociocracy
Apply
2
OpenMoney
MetaMask
Joe’s�Cards
Joe’s�Card�#instance
Create
Accept
MetaMask
Circular Flow
OpenMoney
Joe’s�Campaigns
Write
Joe’s�Campaign�#AI News
Edit
1
MailTrain
Joe’s�NLP Bots
Update
Alexa
Matrix
Feedly