The #bootup protocol, aka #buddha protocol (get the #^@* in here now)
By Brian Vereschagin
#bootup
Abstract: I dont have patience for this shit right now. Title is correct. Follow the instructions below to initiate the #bootup sequence. This is an emergency.
— —
Dependencies:
none
— —
Instructions:
1. Queue up Sound the Alarm by Thievery Corporation, and then Wake Up by RATM, and then post your next ones in the comments.
2. View this image, and this one, while unscrambling your brain, as needed.
3. Maybe find some other documentation.
4. Load protocols into your brain one by one in the following order to understand how they work together: #seedpack, #glossary, #stack, #hiddentemple, #org, #handshake, #cluster, #guildbook
5. Check out the CIC website.
— —
#seedpack
Abstract:
Each individual unconsciously maintains their own list of words and symbols which they are comfortable with using and sharing. In cases where the words or symbols are not commonly known, they can be created and shared as lists. The jargon is negotiated on a peer to peer basis until mutual understanding occurs (coming to terms). A shared namespace allows multiple individuals to negotiate the contours of their community. One special type of entry is a protocol.
— —
Instructions:
1. Maintain a list of vocabulary in memory.
2. Create a list of words which are not well known, but are helpful or required to explore your interests with Others.
3. Save the list. This can be done by storing it on your hard drive (and waiting for ceptr), or by merging it into a shared namespace location (centralized stateful workaround due to low level tools not being available at this time).
4. Include protocols in a sub-glossary, or prefixed with a symbol and appended to the #glossary. (Ideally everyone will keep and share items in a purely p2p way, however, we are forced to use centralized locations such as OneNote, or a website to allow access to each other due to developmental limitations of current p2p tech/software).
— —
#stack
Abstract:
The universe can be analyzed as a series of bifurcation points which have layered one on top of the other with increasing complexity. (eg. atoms, molecules, organelles, cells, tissues, organs, organ system, organism (body). We also share many structures in the brain which enable further layers of bifurcation which continue in this outward direction eventually connecting everything (see spirituality). The #stack may refer to a number of things, but first and foremost, it is the acknowledgement of this layering and how it enables meta-standardization and modularity of the protocols. For another example of these principles in action, check out the OSI model, which underpins the internet and all attached devices.
— —
Dependencies:
#seedpack — protocols are the basic unit being stacked.
— —
Instructions:
1. Create a dependency tree for all of the protocols that you use
2. Notice that certain protocols create bifurcation points and become foundational for expanded complexity into the layers above, and sort the protocols into these layers.
3. Use this concept to interact with the network in a standardized manner; to understand what it means to be a peer in a p2p network.
4. (optional) adopt an existing meta-stack paradigm such as the #hiddentemple protocol. hint: do it.
— —
#hiddentemple
Abstract:
The #hiddentemple is a meta-stack for abstracting the complexity of protocol interaction into layers. This meta-stack includes four layers: #thebody (I), #thebridge (II), #thenet (III), and #theheart (IV).
— —
Dependencies:
#seedpack — this is conceptual framework for the layers of interaction between protocols
— —
Instructions:
1. When creating a protocol, tag it with #thebody, if it involves only instructions that an individual would do on their own. #org is the primary bifurcation protocol of this layer.
2. When creating a protocol, tag it with #thebridge, if it involves only instructions that enable contact and communication (peering) with Others. #handshake is the primary bifurcation protocol of this layer.
3. When creating a protocol, tag it with #thenet, if it involves only instructions for managing the flow of protocol data as a memetic router. #cluster is the primary bifurcation protocol of this layer.
4. When creating a protocol, tag it with #theheart, if it involves only symmetric protocol instructions. #guildbook is the primary protocol for this layer, but since it fills the god slot, there is nothing above it, but it loops back to the individual through full #stack symmetry.
— —
#org (#metaorganization)
Abstract:
Asymmetric protocol instructions require autonomous authority, which is granted by divine sovereignty. This authority is codified in the instructions of this protocol. This is the minimum requirement to demonstrate that the individual is capable of full participation in a peer to peer environment. The individual takes on the meta-organizational structure which conveys the stateless decentralization of the network. Now the individual may be identified in a shared namespace, like having an IP address. It is also fitting to refer to the individual as an #org, because whereas private hierarchies run with asymmetric protocols are seen as the normal form of an organization, using symmetric protocols means that there is no external state required, and the organization is contained entirely within the individual and interacts with Others asynchronously.
— —
Dependencies:
#glossary — Each individual has to keep track of which protocols they will use with Others.
#seedpack — Protocol expression is what allows each individual their voice on the network.
#stack — In order for the individual to understand the network, the layers must be recognized.
— —
Instructions:
1. Name a meta-organization which has discovered the existence of meta-organizations and must name itself in order to become their equal.
— —
#handshake
Abstract:
The #handshake protocol deals with the sharing and updating of protocols between individual #glossaries. Peer to peer networks are made up of many pairs of p2p links, but do not always form perfect many-to-many full mesh typologies. These links are the entry points to the network. Everything happens directly with peers.
— —
Dependencies:
#glossary — Each individual has to keep track of which protocols they will use with Others.
#org — Communication is happening between individual #orgs.
— —
Instructions:
1. Establish a medium to share data with an Other.
2. Compare your #glossary with that of an Other.
— —
#cluster
Abstract:
This is the first protocol in the stack which is bifurcating a partially immaterial layer. Individuals are connecting to each Other and sharing #glossaries in the first and second layer, but now by making a choice whether or not to adopt any protocols within, we act as memetic routers for a protocol network. As soon as more than one individual are sharing media and protocols in common, we call it clustering. A mix of symmetric (stateless, asynchronous holographic) and asymmetric (nucleation of synchronous state) protocols can be openly shared and adopted to describe and improve all aspects of society.
— —
Dependencies:
#handshake — the network is made up of p2p links
— —
Instructions:
-1. (workaround) Establish communications media utilizing an asymmetric protocol to describe a centralized point of contact for all potential peers in the #cluster to share and negotiate a common #namespace. (explanation: we do not have the layer 1 and 2 tech programmed yet, so we cant expect each individual to house and negotiate their own #glossary on a truly p2p basis. If we could do this, we would realize that there is no central material namespace cluster state, but its the convergence of these individual #glossaries which make it up holographically. We just use centralized resources for now, like OneNote, and website. Since this now involves private resources and ownership, aka, state, the protocols describing centralized communications media for the cluster will be called asymmetric. It is critical that we shift towards decentralization with symmetric protocol use asap.)
1. Encounter (or create) new protocols and decide if they are compatible with your motives.
2. Copy to your #glossary any protocols or protocol updates that may be of interest to you.
3. Copy to your #glossary any protocols that will be used to describe your interactions with Others.
— —
#guildbook
Abstract: This protocol describes the guilds system which slices up the various motives of human society based on forms of suffering and forms of joy. Guilds are contexts for individuals to work together. Projects often require a number of different disciplines to materialize. One individual can fill many roles and draw on the resources of many guilds, or many different individuals could meet the various project demands. Guilds represent the aspects of human motivation for working together. We use numogram tech to negotiate and coalesce them.
Just as #protocols are ideally stored in each individuals #glossary, so to is this guild list and data ideally maintained and shared by each individual. Guilds are not material, they are a context of shared motivation to simply do work together. They are aspects of the metanarrative, which spirits the protocol matter. You cannot join a guild, except for accessing resources which are still governed asymmetrically (due to requiring software development like ceptr for the bottom two layers so the plumbing and paperwork can be done automatically, autonomously and directly with peers).
The #cluster protocol set up information flow, the ability for memetic replication of protocols, but there is still a question of what kind of organizations those protocols may instantiate. An exclusive hierarchy could still use the meta-stack framework, and easily convert the symmetric protocols to asymmetric. So there is one more layer to describe which holographically connects the shared human motivations back to each individual. This is the organization layer, and the #guildbook protocol is filling the god slot, which loops back to the individual by being completely self contained (inner symmetries).
— —
Dependencies:
#cluster — memetic propagation of protocols allows for decentralized negotiation and convergence.
— —
Instructions:
1. Decompose various activities into their underlying motives as forms of joy and suffering.
2. Collect these motives into guilds, which slice across organizational and community boundaries, and map the archtypal contours of human motivation.
3. Collect meta-data about each guild.
4. When creating a symmetric protocol, tag it with a guild name to give it motivational context, which can be shared with Others (asymmetrical workaround: centralized guildbook, with a list of protocols under it.).
5. When launching a project, tag it with all of the guilds required to describe the motivational contours for the work to be done.
6. Compare guilds between clusters of low mutual convergence to promote collaboration and sharing of spaces, resources, and information.
Originally published at spectacle.agency. Nov 12 2016
