Protocol: Difference between revisions
No edit summary |
No edit summary |
||
(3 intermediate revisions by the same user not shown) | |||
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. | |||
== 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]] |
Latest revision as of 06:15, 17 November 2023
Introduction
You have learned about our manifesto for the first time in our story. In this narrative, a new intelligence appeared for the first time. We then described and experienced our Manifesto, what unites us and what guides us, in our Handbook. Following that, we unfolded our Big Vision, the shared experience of the manifesto. We transformed this vision into ideas for all areas of life, and we created a new perspective for evaluating ideas. What follows now is our key that will unlock many of the big and still closed doors for us.
The attentive reader could already glean from our dawn letter that the one who contributes the most to achieving our vision in our alliance should also have the greatest entitlement to remuneration and the greatest entitlement to co-determination. Of course, this presupposes that we must precisely evaluate what contribution is, which was briefly outlined in the dawn letter. We therefore need to find a mechanism to measure merit to regulate this contribution in a reward and co-determination system that still needs to be created. It might seem obvious to not want to reinvent the wheel and to rely on proven vehicles that have seemingly already solved these challenges. Think of companies, political parties, or non-profit organizations. In all three vehicles, merit is evaluated, rewarded, and co-determination is organized.
However, in our view, this would merely be a workaround. A term introduced in our dawn letter and often used in the language of programmers. We believe that the organizational forms, companies, political parties and non-profit organizations individually and the market as a whole are burdened with a major problem. So we believe that these organizational forms are part of the cause of the great stagnation. This can be recalled briefly: Since the early 1970s, our entire species has entered a global process characterized by the absence of real key innovations. Thus, to create a real solution, it is necessary to tackle the problem on all levels and at the root. It is said that a good problem description is half the solution. In any case, we want to proceed with as much caution as possible and now in the next chapter, first examine what the problem is.
Problem
We have already briefly and directly pointed to the problem and hinted at it through colorful allegories. So it's time to state it again, clearly and unequivocally. Our existing organizations and the underlying organizational forms are not able, due to psychological, economic, social, and technological reasons, to adequately reward an individual for their contribution to these organizations and provide an appropriate level of participation based on these contributions.
While these organizations may be functional from the perspective of a modern, and perhaps even a postmodern human being, the outcome is subpar. We, those who see beyond and aspire beyond culture, can clearly see that these organizations are essentially, a source of troubles.
This assertion of a problem once again questions the status quo and all common doctrines. This fact is often reproachfully held against us and results in pride in our alliance. Not only is the earth not the center of the universe, other things too are different than we think. We now want to elaborate on the problem in brief, so as not to lose any scientifically faithful and skeptical readers.
Let us therefore first consider in very broad and critical terms the organizational forms existing today: companies, political parties, non-profit organizations, and a newer form - protocol, as we first encountered it with the internet, open operating systems, and digital currencies - in terms of contributions, wages, and participation.
Companies. This organization generally has a binary view of contributions, wages, and participation. The owner receives the profit as wages and determines the direction. The employee receives a salary for their contribution, which is measured in time.
Political parties. This organization cultivates a singular view of the dimensions. The loudest determines the direction. Period.
Non-profit organizations. Here we find another binary view. The one who invests the most money determines the direction, and the loudest may then go in that direction.
Protocol. By this, we mean, as briefly mentioned, algorithmic protocols. Surprisingly, we only find a singular view here too: The person who performs the most challenging work earns the most money. Participation is omitted since a very limited range of actions is determined from the start, and exceeding this range results in draconian penalties.
We now want to focus on one of the prevalent organizational forms that seems most suitable for our project at first glance - the company.
Since the 90s, when Sir Tim Berners-Lee's key innovation - the World Wide Web - reached a critical mass, companies started developing new business models. These models were opened up, as the new communication protocol made many things possible in the digital world that were not possible in the traditional world. Customers, for example, could now become employees, think of social media.
Technology has thus led to many innovations. The causes of the problem, however, remained the same. They were still companies, and the owner still determined the direction. If an employee has a brilliant idea, the machine might pay out a small bonus at the end of the year, but essentially, nothing changes. If the owner succumbs to cognitive bias and points in the wrong direction, everything goes astray. We are aware we may lose some skeptical readers here, but that is the nature of expeditions. Not everyone can fit on the summit.
Of course, we are not the only ones who have identified this problem, and there are several ideas on how to address it. It would be even more surprising if others hadn't sniffed out this stinking mess. So, ideas have been developed to lower the fever and treat the symptoms. These ideas have been adorned with euphonic names like stakeholder value. But the essence, dear friends, remains the same, and the real problem is not solved with this hocus-pocus. Who are we telling this to and how could it be otherwise, since the same causes that led to the problem still exist.
Goal
Although it is considered good taste today, and we reluctantly committed ourselves to it, yes, to include one or another, but rummaging through the dumps of problems won't get us any further! So we want to devote ourselves to our goal with even more passion and joy now. Why? Because we can. Now imagine a friendly smile in the form of a colon, a dash, and a closing round bracket. Enough!
Our goal is to fairly reward and use as a basis for adequate participation the achievements the members of our alliance are making in order to achieve our vision. Our vision is to support our members in overcoming themselves and thereby all of us overcoming ourselves. Up to this point, we have individually examined the personal, familial, economic, political, scientific, and cultural levels and developed a framework for change on these levels, where new ideas can grow. Our framework of change and our ideas on the individual levels were put into words. But we don't want to rest and just enjoy the nice view on this plateau. No, we don't shy away from specifications either. We want to achieve the highest.
To do this, we want to transform our framework for change into a higher form and translate this framework now from language to source code. We want to overcome ourselves and create a software, meaning a protocol that creates changes in a completely new way.
Once again. We want to create a protocol that creates change!
Our goal is to include technically non-versed readers at this point. This may lead readers who are technically versed to rightfully skip over parts.
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.
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.