- While we await the completion of development of the modular Ekklesiapp tool and Sunscrib, which will enable us to customize collaborative and democratic editing of our story, and also to easily iterate on experimentation with democratic decision-making processes, we are currently using the GIT tool. Below, however, are the first steps in a collaborative editing process for our story. This is just one example of the many possibilities to be explored, as the final elaboration of tomorrow's deep democracy is up to you collectively.

- Everyone has the opportunity to propose modifications to any information entered. As it is impossible for every human being to read all the proposals that could be made by all 7 billion human beings. We use an algorithm that takes a large enough sample to represent the entire population. The proposal is then sent to this representative sample. People can vote for, against or abstain, and if there are more than 50% in favor, the proposal moves on to the next level.

- The proposal is then sent to a consortium of experts and elders who will study it in depth, checking the technical and scientific aspects, estimating the resources and time to be allocated, and above all ensuring that it fits in with the established constitutions.

- Eutopia's constitution will lay the foundations of the society, which is studied and justified as a means of achieving our common goal of living a fulfilling and sustainable life in harmony with the Earth. It will then have to be taught to awaken the people to it, to ensure that it guides their proposals and decisions.

- Once the work of the experts and sages is complete, their opinions will be attached to the final proposal, so that the citizen has all the keys in hand to make his or her choice. The people appointed as experts or sages will be elected by the citizens in their respective fields. The transparency and veracity of the information contained in these opinions must be ensured, as well as the simplicity of the information, all to enable the citizen to have all the cards in hand to make his or her choice, and to exercise his or her power with a clear conscience.

- The proposal is then sent out again to a sample group with the information and opinions delivered by the experts and sages. If the proposal is approved again, it is then sent to the whole population for final adoption. The result should then be the same as that of the sample. Nevertheless, when the citizen receives this proposal for the final vote, he or she will know in advance that more than a majority intends to accept it, which has the advantage of giving the citizen one last chance to retract.

- The citizen therefore does not receive all the proposals, only when he is part of the sample and the one that should a priori be accepted by everyone, but he also receives only the proposals that concern him according to the more local or global application of the decision, and the level of power organization established.

- Before you send in your proposal, we also set up a collaborative system that we strongly advise you to use. Your proposal is then first and foremost a suggestion, and these suggestions are accessible to anyone who wishes to participate. This tool, which can be seen as a forum, allows you to debate, gather opinions and help improve your final proposal, refine and correct your comments, and help you with collective intelligence tools.

- You also have the option of delegating your power to someone else, who will then vote on the proposal for you. You will, however, have access to the voting history to check that you are in agreement, and you can withdraw your delegation of power at any time. You can also choose the level of power you wish to delegate to the different layers of the company.

- While waiting for the end of the development of the Ekklesiapp/Sunscrib tool, we are currently using the GIT tool.

- GIT is a tool created by Linux Torvalds to allow developers to version their application code, it is now used by all developers around the world.

- It allows you to have multiple, application versions in what are called “Branches”, usually a branch includes additional features or bug fixes.

- To retrieve the most recent version of a branch, we do what we call a 'pull'. To push our modification onto the branch, we do what we call a 'push'

- Git allows total transparency, because it keeps a history of all modifications and the author of the modification.

- You now need to transform the word 'application' into 'story'. The main branch is the updated story, available online. Another branch is created from it, called 'dev' (for development).

- Everyone can openly present their idea and modify the story in "dev", just retrieve the branch to edit it, then make a "merge request" which is nothing more than a proposal to modify the current version of the branch.

- These merge requests require a minimum number of approvals to be merged; in our case, the threshold is currently set at 70%. During this approval phase, each line can be commented on by others, who can also suggest new modifications, and these comments can be answered.