403
edits
Protocol: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 48: | Line 48: | ||
And now, enjoy our protocol. | And now, enjoy our protocol. | ||
== Basics == | |||
Software permeates all areas of our lives. A map app on the smartphone is easier to use than carrying a paper map around. Sending a text message is faster than writing a letter. Software can greatly enhance an existing process - as in these two cases, navigation and communication. The framework we describe in language, and the resulting movement in you and in groups, can be described as a process that enables change. As software, this process will be capable of facilitating change much more effectively in the future. Every software can be considered as a building and thus also has an architecture. This architecture follows - as with any structure - certain design principles. We will focus our attention in this chapter, which is dedicated to our protocol, primarily on these principles. From these principles, it will become apparent how our structure will look in the future. | |||
== River == | |||
Every building is constructed in a consistent sequence. These individual construction phases, from the excavation pit at the beginning to the painting works at the end, build upon each other and can therefore be described as a river that flows from the source to the mouth. Our software follows this process too. The foundation or source for our structure are values that emerge from our manifesto and that we have laid out in our manual. These values underpin our principles, from which specific functions can then be derived for use. The use generates data from which we can first recognize logical patterns. As the data increases, we can also begin to select suitable algorithms for machine learning from the data. So, one dimension of our protocol is a process that transforms values into software. This process is a unidirectional flow from values to principles, from principles to functions, from functions to use, from use to logic, from logic to algorithms, and finally from algorithms to machine learning. In other words: our river transforms our values into software. | |||
In the following, we will now examine each phase in more detail. | |||
== Values == | |||
Our values are built on our manifesto and are described in our handbook. Thus, our values represent, on the one hand, a linguistic interpretation of our manifesto and, on the other hand, permeate all our actions, thinking, communication, and thus impact. Long-term thinking, appreciation of risks, creativity, and growth on a personal and societal level are values that describe our alliance and that our alliance also represents. Our values were vividly and palpably described in the idea book. | |||
== Principles == | |||
Our manifesto, and thereby also the values derived from the manifesto, are unwavering and metaphorically speaking, deeply engraved in the hardest granite. Ideas are at the other end of the spectrum and are fluid. Ideas flutter around our granite tablets like butterflies. An idea born today and deemed good can be examined tomorrow and found to be bad. | |||
Our principles are located between these poles. Closer to the granite, but no longer unshakeable. Principles thus have stability and constancy on the one hand, but can also undergo slow change. Principles originate as ideas, and bring at their inception a heightened quality that already indicates at that point that it is not merely an idea. | |||
Once a principle is recognized as such, a function can be derived from it. We will discuss functions in the next chapter. Since ideas are fluid by nature and also due to psychological dynamics we have already described, for instance, a principle of our alliance is the priority of written communication. This means that communication should always be written as much as possible. Communication also includes the dialogue with oneself. A function now allows our alliance to collectively log ideas in a service we call ULTANIO Mind. | |||
We now wish to describe some of the core principles in the following. The goal at this point should not be to fully describe all our principles, but to provide a view of sufficient scope for our protocol to be understood in its entirety. | |||
Our principles thus form a network that has a certain dynamic. Individual principles can be like nodes in a network, linked to other principles, or they can be singular, that is, without connection. From the number of nodes, a certain hierarchy arises, which can cautiously be described with the terms main principles and sub-principles. | |||
In the following we want to take into account this hierarchy only to the extent that we pick out and describe the eleven principles important for understanding the protocol. Some other principles can be taken from the previous chapters and are not listed separately here. Other principles still remain hidden from the reader and he will learn about them in due course after joining our alliance. | |||
[[Principles]] | |||
== Functions == | |||
Let's recall: One dimension of our protocol is a process that transforms our values into software. In this process, values therefore flow into principles from which functions are derived. | |||
Our functions as part of and as a phase of the process can also be described as action protocols. These functions are therefore partial reference implementations of our entire protocol. | |||
Next, we want to highlight two such action protocols and specific implementations that we practice in our alliance, and describe them as examples for you. | |||
=== Ideas Dinner === | |||
An Ideas Dinner is a regular conversation format where we invite selected guests, candidates, and members of our alliance in metropolises such as Berlin, Zurich, or London, as well as on the sidelines of conferences such as in Davos, for a joint dinner. Each participant brings an idea to this meeting. The ideas are presented initially by the participants. This is followed by a moderated discussion where the ideas are explored from various perspectives. All ideas are summarized in writing after our dinner by the respective leader who organized the dinner. If interested, we establish contacts between the participants and also accompany the progression of the ideas. | |||
So, at our Ideas Dinner, every participant can surely take away many new ideas. Moreover, these Ideas Dinners are an opportunity to personally experience our protocol at a dinner, and they act as a springboard for ideas, as ideas are now shared, enriched, and promoted. | |||
=== Mind === | |||
We've already briefly mentioned our software ULTANIO Mind elsewhere. This prototype makes it possible to document your ideas in a web-based software and share them with your tribe, the federation, or the public. Mind evaluates and analyzes ideas based on artificial intelligence, rewards good ideas with ULTA, our currency, and makes suggestions based on artificial intelligence for further ideas that could be enriching. In addition to these core functions, we have already turned many other principles into source code, such as the principle of ascent, the principle of adventure, and also the principle of history. | |||
== Usage, Logic, Algorithms == | |||
Through the usage of our features, not only unique experiences and many ideas are generated, but also a lot of data. Our endeavor is to learn from this data. On one hand as humans, and also through algorithms. In the beginning, we promised to include even technically inexperienced readers, and we want to keep that promise. The aim of this book is not to provide a complete and detailed insight, but rather the goal of this book is to convey an understanding and a comprehension of what our protocol is today and, above all, what our protocol will be tomorrow. | |||
We are excited about everyone who is now interested in contributing to this protocol. Every question is already such a contribution and we are also happy to share the existing source code with all members who have technical interest beyond that. Over twenty thousand exciting lines of code are waiting for you. | |||
Let's pause here for a moment and see where we stand. | |||
We have described a problem that we want to solve in the future and we have also described the much more beautiful side, our goal. We have also described principles and features that we have created. | |||
Finally, we want to give you an outlook and describe the problem areas that arise before us and on which we are working to solve them. For this, we are sharing our so-called Halloween Letter with you. | |||
[[Category: Protocol]] | |||