403
edits
Protocol: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 53: | Line 53: | ||
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. | 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. | |||
== 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. | |||