1) PURPOSE: The purpose of the platform is to maximize the well-being of everybody within planetary boundaries. This is something that cannot be changed. Changing the purpose, as systems thinking tells us, breaks the tool. If citizens want to change the platform’s purpose, they have to build a new tool from scratch and call it something else.
2) DESIGN: The designers are responsible for articulating how the stated purpose is best achieved. They design the intricate mechanisms that together form the system that comes as close to achieving the ideal result as possible. This book contains the platform’s first designs. The design should be modular in nature, meaning that various components can be designed separately and then integrated together. Various design teams create their own variations of the individual modules and the system as a whole in their quest to perfect the system. Design teams can copy modules directly from others, but all components must be credited to their original creators and contain their edit history. When the designs are ready, they are passed onto the coders.
3) CODING: The coders take the designs and principles articulated by the designers and turn them into open source code that can be scrutinized by the public. They work on the ideal expression of the designs using computer language, but refrain from contributing any designs themselves. Some coding teams specialize only in creating specific modules while others specialize in integrating the modules into whole systems. The designers oversee their work, but can’t contribute any code themselves. As the coders are the people who ultimately inscribe the constitution, their work needs to be clear, simple, and beautiful.
4) SIMULATION: All designs and coded components are subjected to thorough analysis and a battery of standard simulations by neutral simulators. The analysis and the simulations try to determine what the outcome of each design and component is compared with their variations. This process produces public reports on the benefits and drawbacks of each design and code.
5) SELECTION: Based on the designs and their reports, citizens have the ultimate say on which version of the software the community should use as their platform. This should ideally be decided using the global echo protocol that seeks consensus, but if no consensus is reached, the decision can fall back on a majority vote. While citizens choose which platform they want to use, the design and the coding process itself is not subjected to the democratic process due to its complexity. The same way drivers can choose between cars and customize many aspects of them, but how the engine should be constructed is not up for a vote.
6) ADMINISTRATION: Once the global community has made their choice about which design they want to use as their platform, administrators are in charge of operating the software and making sure it runs as intended at all times. Their task is to ensure that nothing comes between the user and the software, be it a sophisticated hacker, rogue insider or malfunctioning piece of software. The purpose is to guard the sanctity of the software and the code. Administrators cannot change the code in any way. All changes to faulty code need to be performed by coders based on public requests. Larger changes are referred to designers.