100% community driven government, socializing, organizing and banking system.


Note that everything written here is only a direction!
Everything is up to discussion and needs your knowledge and input.
The All-System is a movement, it lives and dies with those that support it!


The Idea
A Worldwide digital government, socializing, banking and organizing system that is hard to corrupt, dynamically changeable and rewards the work and ideas of every individual using the system.
Users can be anonymous, identified or anything in between and can still earn money and have credibility.


How the system works:

This provides a bit more details, but you can Skip this part if you have read the Introduction.

A group of people start creating a prototype which will have many flaws but will be adjusted until it runs smoothly. At first there will need to be some beginning/ground rules that have to be agreed on to get the system running like: This and that feature are untouchable unitl the system has been in existance for at least 5 years and has a usercount of at least one million users. Everything I have written down so far could be used as the begginning rules. After that time/usercount it becomes dynamic and 100% of it can change with the decisions of the community that uses it.

The systems code and blueprints for hardware are created and modified by a group called the Core Developers and shared by everyone using it.

!!!Profile example Picture placeholder!!!

Every user or group has its own profile. The profile can consist of the users chosen Name, an ID, the users support values (supported work/projects that has been shared on the profile) and other data that is critical to the system and the user. Only the Nickname and ID are visible to everyone from the start. Everything else is only shared to other users by choice. Most of the content (pictures, videos, audiofiles etc.) that is added to the Profile is a link and leads outside of the system. This may change in the future but in the beginning the system integrating all data would be too to handle.

Users can share what they do, what ideas they have via their profile and other users can support that work/idea.
The work can be anything: manufacturing wares, reselling products, planting trees in the desert, playing video games, painting pictures, coding an application, absolutely anything.

Users can form groups and even form groups inside of groups.
There could be a group USA with subgroups inside of it being Texas and California etc.

Groups can have rules (Digital Contracts like: Users that want to be part of the group USA need to identify their account with a real name, birthplace, choose a subgroup of (current residing location), fingerprint, DNA data and pay 20% income tax a year. Which is distributed to the groups USA with 5% and (current residing location) 15%. The group (current residing location) distributes its money to the subgroups: police, hospitals, schools etc.

.aProfile
Every user can completely customize their profile, users will have the option to add/link chat boxes, guest books, websites messengers etc. to their profile. The difference to social media like Facebook, Twitter and YouTube is that the user can decide to stay anonymous . The users doesn't need to share anything. The profile just shows an ID if nothing is added or enabled to the public.
Users can also choose who to share their profile information with. They can use premade or their own white and black filter-lists, share everything with everyone and later then add specific users and groups these lists.
Or only share certain things with specific users or groups. Anything can be changed at any time.


.aSupport
Anything a user, group or project does or shares within the All-System can be supported by users.
Users can support a user or a group and/or projects within that group, something the user shares, a promise with or without a contract, content created, a project delivered etc. All these things can earn a user or group support-points but only if it is shared with the public *Optional: certain groups.* Support-points have no max cap. The only way to loose these is when users decide to not give support anymore or when too many of them are collected the aBackflow might reduce the amount.
*Optional: Get them removed if you are put on the Pillory/Court for missusing contracts, fraud or abuse etc. and found guilty. I don't like this because it can be misused. Even if there is a court and the user has been sentenced users themself should decide if they stop their support. The court should have the ability to notify all users that the user has been sentenced and give details, present proof and let users decide on what to do with that information.

Groups and projects have their own support stash/wallet that is sperate from the users that are in those groups and projects. Groups need to be able to collect higher amounts of Flow than single users.
It means that the aBackflow allows higher amounts of Flow to be collected via a Group. The support of a group only affects active users in that group.

Support values for projects and overall support are not visible to others.
They only become visible if the user enables visibility to others.

-Support is not Flow, support does however transfer Flow from a user to another user or group.

It works like this:

The user specifies an amount of Flow s:he is willing to give to other groups/projects or a user.
This could look like this:

Tansfer 1 Flow for every support point I give. OR transfer 1%  of my support allowance of 10 Flow for every support point I give at the first day of every month . OR transfer Flow from my support allowance % to the support points I have given. There are many options here but the community needs to decide which one to use. The standard support should be quick to use and low maintenance. Complex forms of support should also exists but be optional to the user.

-There need to be a limit like 1 coin per support point. This would allow a user a maximum of 10 coins per support.

-If a group is given the privileged label (the whole community voted) the group will also recieve aFlow directly from the aOcean through aRain.

aSupport values
There is no negative support only positive 0 to 10.
Support can be changed anytime by the user that has given the support.
The more support points a users gives, the more Flow a group/project or user will receive from that user.
Accounts with 0 support can support others but until the account itself receives a certain amount of support it will not influence any Flow transfers from the Ocean.
Users have the option to disable support for anything or everything they link in their profile.

-Flow bound to support-points needs to be an amount over 0.

*Optional: Negative support values (-100) can only occur when aContracts are involved.
You wager your own credibility with an aContract to gain financial support for example.


.aGroups
Users can form groups. A group is a list of users with their own ID and profile space. A group can be anything a continent, a country, a club, company, etc.. It can follow certain goals: Play video games all day long, create Video games, create Art, make music, plant trees in the desert, produce candy in a factory, resell dolls, anything is possible.
The group can be managed by the creator of the group (dictator mode), or a leader that has been elected by the group or the group manages itself. The managing style can also be changed at any given time.
There is the ability to roll back settings and depending on the managing style of the group: The creator (in dictator mode) can change a users permissions or remove a users from the group. In group managing mode users vote to change permissions or remove certain users from the group. etc.
There are limits like dismissal protection when aContracts are involved. A group can gain support in form of donations and normal support which is then shared by the members of that group by the aContract that has been agreed on. Users receiving support and Flow from the group can only be removed or get limited access to the group if they fail to do the things they agreed on in an aContract. Users can be assigned roles and duties. Opening up to the public how the money is used/distributed inside that group or project is up to the group or project. *Optional: Flow donations and payments made to a group or project are openly visible. That means everyone can see how much money has been collected on the groups profile.

-Groups where users can join as members without using aContracts can not recive nor fund members?

-Every user is part of the root group All-System.

-It is not allowed to use a groups funds for private matters. Everyone needs to have an assigned wage even if the value is 0 or 1.000.000 a month. What is left after paying everyone is the groups property and exists to advance the group (research etc.) or wages need to be adjusted. If not used it will aBackflow back into critical parts of the all-system. It is not possible to hide a wage from other member of the group everyone can see what everyone earns. Even if the group is in dictator mode once a group has been created it is not the creators solemn property anymore and thus needs it's own resources. The creator (in dictator mode) needs to give himself a wage and is not allowed to use the groups funds privately.
A group owner can not sell that group s:he can only lead it and earn his/her wage or give his position away. The group will exist as long as others support it, with or without the creator of that group.

-Why groups aka companies should not be sell-able:
We are in dire need of real leaders! Groups should be about building/advancing technology or supporting humanity and life in general. If groups can't be sold the group will be more about the purpose of the group than people owning it. If one cannot own that group the only thing left is to lead it! It might be a harsh change to some but it brings a lot of positives with it.

-Merging of groups is not possible. To merge groups a new group with a new ID needs to be created and memebers have to abandon the original groups.


The different forms of group managing modes:

Dictator : Creator of the group (decides all), can give away his position.

Leader: Is voted as a leader by the groups users (decides all), cannot give away his position only step down.

Random Selection: A leader or other positions are filled with a random selection of the groups userbase. Users selected can decline.

Group: The group decides everything as a whole.

Group with Delegates: The group votes for and assigns delegates to decide on certain tasks.

-Modes can be changed but permission to change it depends on  the current mode.


.Groups with privileges
A group with privileges is a special group that is voted for and essential for the all-system community.
Like the Core developers, without them the system does not function. Others could be Farmers, police, hospitals etc. The group will recive Flow directly from the system itself.


.Projects
Projects are worked on by users or groups and when the project is finished, it is shared with the community or parts of the community. If the task/project has not been done by a single user, support and donations are shared defined by the aContracts used.

A projects content (files) can be private until released. This is important if the group creates a movie, game, series etc. The project files can also be shared from start to finish, it's up to the group.


.Crowd funded Projects / Funding request
When a group or project seeks financial support. They can open a funding request with an optional aContract and if people like that project idea/contract they will support it.

The difference to current crowdfunding platforms is that here nothing needs to be offered in return to those that fund a project. Exept if aContracts are used.

The user or groups support/credibility is at risk though. If the user or group fails to deliver what has been agreed on via the aContracts, like when a user screws up, goes back on a promise or plainly scams their supporters. The group and users inside the group will lose credibility as specified in the aContracts and depending on the aContract owe Flow to their supporters.

A user does not have to reveal their real identity but in some cases (if the user needs a lot of flow or support) they might need to reveal it to fulfill an aContract in order to gain enough support or flow.
If a user does not want to take such a risk s:he can casually ask for support in his/her profile or group and when talking to other users. If the user has not enough support to gain support s:he can ask other users to vouch for him/her and add them to the aContract.


.aRequests
Any user, group or project can make a request. Exacmple:
I/We need a 360 video of a tree and offer a reward through an aContract for the completion of that request.
That kind of request can be made public and others that want it to be created too can join in to finance it.
Whenthe request is fulfilled the user, group or project that fulfilled the request will gain the Flow (digital money) via the aContract.

Arequest can also be fulfilled or made without aContracts but doing so forfeits any legal backing.


.Promises
A user, group or project can promise to do/deliver something. Users can support the promise but unlike a funding request support can only be gained not owed. When the promise is deleted any support gain is then forfeit.


.aProposition
Is used to introduce new features and rules. Can be created by any user or group through their account/profile. It will first need a certain amount of support points to get into the voting phase.


.aPetition
Works the same as aProposition but is used to change existing features and rules.


.aFeatures
Any feature liked or disliked by the community can be made permanent, optional or be removed.
Every user can vote to change something and gain support to do so. When the change reaches the needed percentage the core developers then have to make the change.

The knowledge limit feature protects against brainwashing the masses to change a core feature in a bad way.

To further protect critical parts different % need to be reached to change a feature.
Very imprtant parts will need an 80-100% yes (change the feature) vote.


.Security
Public/private key cypto and encryption will surely be used but there is a lot to account for. Security experts need to discuss this and find good solutions.
Airtight security/features to protect against account hacking, id stealing, character assassination, blackmail, extortion etc. are needed.

I will add some concepts that I think could work but I'm sure they will be less then airtight.

- Users and groups that are created have their own ID and private-key


.Abuse
Users/groups/projects seen as illegal, abusive or in any other negative manner cannot be removed.
But they can be put on filter-lists. These lists then can be published inside the system.
Groups can make using these list mendatory to stay a member of the group. Since users can have multiple accounts they can still be access that information with another acount if they really want to.
A bit controversial but needed to protect freedom of speech.


.aContracts
Digital Contracts that are legally binding. Aka I give you X money if you build a wooden shack with this and that. A contract can be with other users, groups or projects. These contracts can have different steps aka no money when there is no shack, a base amount that is paid even if nothing is done.
If it is not as agreed upon, if the contractor gets ill and can't follow his contract time will be extended or only certain amount is paid etc. the contract can be as detailed as wanted/needed.

Only contracts/parts of contracts approved by >50% of the community are allowed to be used inside the system. To protect against obfuscated contracts and traps, hidden details etc. Contracts my need to follow certain rules set by the community to keep both sides safe from fraud/scam.

Users create aContracts by using predefined "aContract blocks" that have been approved by the community.
Custom "aContract blocks" may be used but only if approved by a professional who risks his support and credibility on the genuinity of that custom aContract. Otherwise custom blocks need to be approved by the community first.


.User account
User accounts have an unique ID (bitcoin like address)
This way users can be anonymous, have overlapping usernames and can still be identified.
A new user is not allowed to give any kind of support or vote. First s:he has to prove the community to not be a bot. S:he will receive some small automated tasks that bots can hardly do and/or then be assigned 5 to 10 random users that are willing to test the user by talking with the new user. These users then vote if the new user is a bot or not. After that the user has to gain credibility through their profile and interacting with other users.


.aFlow (digital money)
The systems own "crypto/digital currency" that is bound to a users account ID.

Bitcoin as it is now is has some serious flaws:

1. Users themselves are responsible for keeping their money safe.
Which is not possible for users that do not have the right IT knowledge.

2. no protection against private key theft.
3. dust slowly chewing away at the coins
4. high energy cost to create the bitcoins
5. bad distribution / monopolization of coins (criminals that started using bitcoin early and some countries using server farms to create bitcoins are to blame)

6. Bitcoin has a limit of coins and is traded thus resulting in very high fluctuations on how much a bitcoin is worth in other currencies.

7. The Satoshi Stash that is about 1 million coins + the NSA Conspiracy surrounding bitcoin

I think that cryptocurrencys are the future but as long as people can "play"with that money it's not very usable. We need a stable currency that can be used for everyday transactions.
I hope that Flow can be that stable world wide currency in its final form.


All-System's Flow has several different features to make it more usable:

1. Users can use/pay other users or groups to protect their account.
2. aBackflow feature that moves currency that is not used for a very long time back into the system.
3. Negligeble energy cost to create coins.
4. Fair distribution of currency.
5. There is no shortage of coins since it scales with the community.
6. No or very little fluctuations of purchasing power since Flow is backed by time.
7. The Ocean is open and everyone can see where the funds are transfered to.


The multi signature feature protects against an illegitimate transfer of funds.
It is an optional feature where other users or groups check if a transfer is legitimate and the transfer is only done if these give their OK. As an example user1 (husband) adds user2 (wife) and Group (transfer check automated) to the list of transfer checkers. User2 and "transfer check automated" get a message about a transfer with the sender, receiver, amount and comment: “Payment for red race car No. 42'. The group “transfer check automated” is a group of hardcore security fanatics that have developed a mobile phone transfer check app and run a server that sends husband a message on his cellphone where he can accept or reject the transfer. Husband and Wife accept the transfer and the transfer is send. A user also could just make several accounts one with all of his funds and several that are only used to accept or reject a transfer.

-Like the name Flow suggests the currency is meant to constantly flow. It can still be used like normal currency but the continuous flow of microtransactions through the support feature is what makes it truly special.

-Slow aBackflow/taxation is implemented to redistribute dust and forgotten Flow on accounts that are not used anymore (dead but not declared dead) and to protect against monopolization/hoarding.

-Flow is scale-able and adapts to the user base. Whenever a user joins the system the Ocean receives a fixed amount of Flow that is then slowly distributed to all users.

-One Flow is worth exactly 1 hour of simple work.

-The more support a user has the more Flow he receives from The Ocean. *Optional needs to be tested before it is implemented

-There is a limit on how much one single member can have on his account. The cap will proably be something like 50.000.000 Flow. But this number will not be static the aBackflow needs to increase exponentially so that that high amount cannot be reached.

-The aBackflow is influenced by the users support of things. The users can choose to a degree where the Flow that is removed by the aBackflow flows into.
*Optional needs to be tested

-A Flow (coin) remembers where it has been and only will Flow into an account again if it has visited enough other accounts. This is a protection against moving the Flow around to work around the aBackflow. *Decentralized approach


Different approaches on how to implement Flow:

Centralized: Multiple servers work on the same tasks and compare each others data. When a user has gained a credible account the servers create a fixed amount of coins and spread them into the system. Not to just to the new users account.

Decentralized: A user gains a fixed amount of coins when he gains a credible account. Those coins cannot be used by the user directly but have to be spend by the user through the support feature.

There is no first come first serve, it does not matter if a user is there at the start of the system or joins later.


.Trade
Trading with users using the system is possible but since every user that creates and uses an account is subject to the systems rules it is not possible to trade the systems own currency with other currencies.
It is not allowed and to further discourage trading Flow with other currencies the system will have it's own currency exchange. There any other currency can be exchanged for 1 hour minimum wage of that currency. If two or more factions/countries share the same currency and have different minimum wages it is leveled out to a value inbetween the difference of them. If there is no minimum wage or it changes too often, a fitting value will be calculated for that currency. (the middle of the difference)

Now you might think that people would buy it cheap with a currency that has low market value and sell it at a higher price in a currency with higher market value. The exchanges do not buy back Flow. This makes Flow useless/worthless outside the all-system if it is not used as one hour minimum wage.
Which is intended, Flow needs to be outside the current market system to work.

The foreign currency that is collected by the all-system currency exchanges is used to trade physical wares or pay services in that country. If a country does not accept its own currency, currency exchange and trading will be stopped with that country.

If other factions/countries do not seek to manipulate or corrupt the all-system and accept that one coin is worth one hour of minimum wage, trade with users of the system will be possible.
This process would be as followed:

A country or traders of a country would create their own accounts/groups in the all system and use the all-systems currency exchange to convert their currency into Flow, to then use the Flow to trade inside the system. Since they cannot sell the Flow back for their own currency they need to trade it into physical wares or services.


.aOcean (the main supply, the systems bank)
Every accounts Flow is aBackflowing over time. This means money not used goes back to the Ocean which automatically distributes a fixed sum evenly to all accounts through aRain, priorizing previleged groups. Previleged groups would be farmers, hospitals, police, etc. Generally speaking all positions that are important for the system or the community but also can include work that needs to be done but has nobody that wants to do it. Thus making the task more interesting by rewarding it better.


.aBackflow
When Flow is stagnant for too long or too much of it is gathered it will automatically flow back to the Ocean from where it is redistributed again. aBackflow is a very critical part of the system it keeps users from hoarding too much wealth. Money that doesn't flow is money missing and that missing money creates a lot of problems.


.Core Developers
All users can share and monitor the system core, but only those that have been voted for as Core Developers by >50%, can change core features of the All-System. Every change needs to be allowed/initiated by the community with at least >50% vote or more depending on what is changed.

Coredevelopers have to compile and apply their code individually (it is to be the exact same code) and the code needs to be reviewed, tested and compared by others first. From there it is distributed to everyone else. All users need to be given access to the code so that every user can compile it themselves if they wish to do this.

Users can choose to automatically receive updates from the core developers servers.

Note: The Core Developers do not control the system! They are just paid developers that are under strict rules and supervision.


.Knowlede Limit
To protect the system against a brainwashed community that would lead to a corruption of the system. A proof that the user understands the change will be needed. To allow the user to be able to vote on a topic actively. That proof works like this:

Every change will have a category and every category will have specific knowledge tests that are created preferably by universities. These tests then need to be approved by the whole community.
When a user passes a test they will recieve a label and be added to one or several indexes as proof that they are knowledagble of a topic.

*Optional might also include a personal meeting with several professionals that vouch for the genuinity of the passed test.

.Tests / Testing
The tests need to be created by the prototype community. To make sure the first tests aren't written in a way that only reflects one mindset or faction there are several options for the creation process of the tests:

Categories that need testing are established first. Then:

1. The prototype community decides on tests as a whole where every vote has the same wight. There is no knowledge limit thus it is important that the prototype community is very knowledgeable. Every individual in it needs to be able to see/accept other perspectives even if they conflict with their own.

2.  Users test each other one by one and either give the other user a pass, fail or they abstain. When a user gains >50% passes than fails they gain the ability to be a delegate in that category. The tests are created and then voted on with the All-System already running in the prototype community.

3. Factions inside the prototype community with opposing views are established and each create a test or list of points that they want included in the final test. A draft that includes all viewpoints is worked out and changed/adapted until all factions sign off on the draft. Afer that process it will become an established testing method for the whole community.

I personally would like to see a mix of all 3. A prototype community that is very knowledgeable and open minded. Consists of factions with opposing even conflicting viewpoints but accept the other factions existence. The factions each create a test/list and then all factions work together creating a test that includes all viewpoints.

If a user fails this test, the user needs to trust his vote to somebody that did not fail the test. If there is a test in place it needs to be easy to understand and can't be obfuscated, that's why it needs to be changed until >50% of the users agree with it.

.Prototype Community
The prototype community are going to be the first users and initial creators of the all-system.
The developers, alpha and beta testers so to speak.


.Prototype
The initial creation of the system. It will be more like a simulation or a game, full of flaws and will constantly change until it changes into a usable system.

If intentions / the goal of the system are known by different factions/countries they will hopefully try infiltrate and corrupt the system. This is wanted and if not done needs to be simulated.
The system needs to change with every attack and corruption it receives. The corruption helps the system to evolve.

Being hard to corrupt and changing when corrupted is the main goal of the system. For this to work the system needs the practice. If the system fails in the creation process it will have to be recreated with a different approach and if it already exists just parts of it need to change for it to become safer and more stable to use.

.Code
Any code, especially for the core needs to be clean and well commented and documented, no bloated or obfuscated code is to be approved. Any corruption attempt of the core needs to be punished severely.


.Blueprints
Blueprints to open source hardware that is created by the community to ensure safe hardware without backdoors exist for users to run their accounts on.


.Hardware
Open Sorce hardware is as important as the all systems software. Corrupted hardware can be used to gain access to group and user accounts and can lead to a complete corruption of the system.


.Core System
The base files needed to keep All-System going. They will be shared decentralized. The user can decide to share/host the core system files or use files that are hosted somewhere else. Users automatically gain a bit of Flow by sharing the core system.


.Core tasks/core positions
Maintenance of the system, testing new users for bots etc. these are rewarded automatically by aRain?


.Voting //write more in here
Imagine Politicians in a permanent state of election. Users can vote other users to be given certain positions within groups, projects or the core system. This vote, like the support can be changed any given time. Votes are anonymous as long as nobody has access to the account.

As an example: User “IQ200Dev” has applied for the position as a core developer and has been voted into position by more than 50% of the community because of his awesome video in which he showed off his coding skills. Later the community finds out that the video is fake and he looses 30% of his votes. Thus he is removed from the core development group and will have a hard time getting into it again.

-To vote, a certain support value or proof of identity is needed.

.Delegates
Delegates in the All-System are very different from the traditional delegates like politicians. Every user is/can be a delegate. There is no option to not be one. Users just trust their full or partial (specific categories) voting power to another user. The delegate then automatically represents the user that chose him. This could be done without the delegates knowledge, imagine it as "vote the same as that user".

With this type of delegate, the passive voting and knowledge limit create a network of trust and knowledge that can make very precise and effective decisions.

.Applying for Positions
Groups can create positions that users can apply for. Users within that group then vote for who gets the position, if a leader or manager is not active.


.Trusting / Passive Voting / aDelegate
A user might want to give his voting ability to another user that he trusts will make the right decision for him/her. Pretty much what we currently do with politicians, but in a functioning way. As our current system isn't working. This can be out of sheer laziness, inability to understand what is voted for, or any reason.
"The difference is that the user can see in detail where his vote has gone to and change the trust and/or vote himself any time." *Not sure about this since it enables the user to see what another user votes.

Some votes especially the votes for core changes have to be made by every user in a specific time frame, if the user does not vote in that time frame s:he will be warned and it will be suggested to trust the vote to another. If a specific number of these warnings are reached the account will be put in stasis and only be usable after the votes have been made or passed on.

An account that goes too many times in stasis will loose credibility.

Problem: If users can just trust their voting power or certain votes to another person without that persons knowledge of it. The user trusting then shouldn't be able to see where his/her vote has gone to, to protect the trusted users privacy. On the other hand there could be an option where users make their voting open to those that want to trust their votes to them.
This would make it possible to trust an politician/delegate with votes". Since votes are dynamic and a politician/delegate only gains power through others trusting him/her, buying that delegate or extortion will probably not work.


.Vouching
Since users have to provide proof that what they do is genuine they can ask other users to vouch for them. This means that a user risks his own credibility to make another credible. Should only be done if you are sure that the other user is not misusing you.


.Multi signature
Enable other users(accounts)/groups to cosign a transaction before it becomes valid. Using this or an All System "bank" is a must against private-key theft.


*optional .Pillory/Court
All-System Feature that needs to be tested: If a user has gained support and Flow by scamming/fraud or other bad misbehavior the affected users can decide to put that user on the Pillory/Court.
Here the scamming/frauding user can justify himself and give promises and contracts to redeem himself.
If unwilling to do such promises/contracts, if proven guilty, the users account id will be added to an index together with all info on the case. It is visible to the public.

Note: Very controversial and I don't like it at all but I haven't found a better way. Everything else would involve others being able to limit or modify other users accounts, which would completely corrupt the system.


.Examples
A group can be a bank that manages users Flow and a user Supports/pais the bank bound with an aContract and the bank keeps his money safe and monitors transactions to protect against theft etc. Since every user can only have positive value of Flow the bank can lend the user money bound by an aContract.

The old way Banks work does not 100% translate into the all-system because of the aBackflow feature.
Thus banks have a different role in the all system, they don't manage the users funds directly but protect the users account and/or transactions.

A group can be a factory producing products but in the All-System a company does not need to sell products to survive, it can survive by support and donations alone.

A baker could offer an open aContract in his profile in which he promises that he uses the money that is given to him, after subtracting his living expenses, to bake bread for free to everyone that visits the shop with a limit of 1KG of bread per person, until the supply is depleted.


.Blocking
Users and groups can block other users or groups. Trust- and Block (White and Black) Filter-Lists can be generated and used to filter profiles and/or profile content. These lists can be private or public.


.Positions
Standard positions are core developer, group creator, group manager/group leader. Custom Positions are possible.


.Graveyard
A user is declared deceased if the account isn't accessed in a given time (1 to 5 years?). aWill is executed if attached to the account then the account is moved to the graveyard where it can be accessed but not modified. Any kind of payment/Flow to that account is disabled. The Flow amount that has been added to the system via creation of that account is removed from the Ocean.


.aWill
Digital Wills that are executed before an account is moved to the graveyard.


.Limits and Security:
In order to ensure critical parts are not changed easily, some features need very high voting percentage not just over 50% but 80% to 90%


.Laws
The All System will integrate all common and needed laws that we already use worldwide. BUT they will be reworked to their essence: obfuscation/bloating will be removed. They need to be clear and understandable.
It can't be that laws are this overcomplicated, we need too many different lawyers, that is not healthy.
Any law should always be kind in nature. Hard and unforgiving laws will create hard and unforgiving humans. Laws exist so that we can live together not divide us!
Instead of sentencing somebody to death we need to put them in a facility where they will get help and if they do not want to change to be able to live with everyone they can stay there indefinitely until they hopefully become kinder in nature.
Crimes are done out of selfishness, hate and greed. It might be a spur of the moment, a psychological problem and maybe even disability of some sort.

All we need are laws that help these people we do not need any other laws. We certainly do not need laws that are supportive of unhealthy greedy and selfish behavior. 


Optional:
.Sharing(ideas, projects, files etc.)
There is no copyright, anything that is shared inside of All-System can be used and modified by anyone.
The only rule is that the original creator(s) need to be credited/linked in the system. Original creators then automatically gain support through the edits/modifications.
Anything shared can receive feedback, support and receive donations from the community or use other support options in their profile. Every user using the All-System can share anything they want.
But this does not mean that it will stay visible, if the community deems it as not worthy of support like viruses, malware abusive material etc.) it will receive 0 support and users can choose to block it from being listed/shown to them . *Optional: (Sharing such files will also make you loose support?)
You can link anything even files that you did not create, but you can't take credit for them, you have to accredit the original creator(s).
But don't worry you can still earn support for sharing it. Note that the All-System does not contain any files except the core files. Everything is a link in the profile that leads to other systems.

Note: This can create conflicts with creations from people that use other systems. One option to fix this could be leaving an option open so that when they decide to join the All-System the work/files/ideas can be linked to them and they gain the support that they deserve. Another would be that if they absolutely refuse the all-system, but the community decides to still give them payment, physical contracts that reach outside the all-system coupled with physical wares/labor could be used to solve these kind of conflicts.

.Edits/Modifications
Are files, ideas, designs, items etc. that have been changed, you can take credit for the change but have to link to and give credit the original author/authors.
The more popular an edit/modification is the more support the original creators receives.


.Misc/Todo:
-things that cannot be shared with the public, as in dangerous chemistry formulas, weapon blueprints etc. might need a special permission to be viewed. One that is granted via psychological evaluation combined with the right training and profession. To make this work a root blacklist needs to be implemented

-Concerning long term users that have very low or negative support due to bad screw ups or just receive low interest from the public. In case the All-System becomes the dominant currency/global system:
Users that do not receive enough support/rep but have a legitimate profile will need to get enough funds to be able to live. Meaning something like a base icome would be implemented.

-The All System when it has become the dominant global system needs to make sure that every individual using it receives nourishment, a place to live and access to the all system. 

-Positions/Work that nobody wants to do will be paid the highest. If the positions still aren't filled, the work will be done by machines/AI, until someone is willing to and has needed knowledge to fill that position.

-As the WWW changes over time so will the All-System. Many positions may need an AI assistance in the future. The All System might need AIs that counter other AIs corruption attempts to be secure.

-The role of Banks changes into digital security companies. Which they practically already are. A user can pay a bank which in return will make sure a users profile and Flow are secure.

-Current Politicians will take on roles as aDelegates and will have to fill positions offered by the system or groups.

-Banned users: If the All System is the dominant system. A ban will be equivalent to a disabled person that cannot decide for him/herself. That person will be assigned a caretaker if that user still wants to participate in the system.

-All initial account settings are protective of the users privacy, the user has to change the settings to share his/her info with others.

-The GUI is not integratinged GUIs have be created with the same rules that apply for the core.
This way there will be a variety of GUIs for every users needs. 

-Bulk discount needs to be limited! Depending on the production method 1 or 1000 of a product need to be about the same price. It can't be that a piece of software costs 100 currency and 1000 bulk discount 20 currency a piece. Even if the software is put on a medium like a CD and producing thousands is cheaper,
a difference like the 80% is what is destroying small business owners. Eliminating specialist that would make their hobby into their job. Killing diversity and forcing people to work in underpaid depressing jobs, which practically are modern slavery. This simple change will create many jobs and happy and healthy people. Diversity and small specialized shops will be available again.

-Create Internet 2.0 in combination with the All System: 100% decentralized internet where all data is shared by everyone using it. No monopolization of data or data flow!

-bountys are given to anyone that is not a coredeveloper if the user finds critical flaws in the system. Coredevelopers adding such flaws on purpose need to be punished severely.

-add credibility value to user profile and add to whole document

-Supporting a user automatically will set the users aBackflow flow. A user can also define how much of his money is used daily/weekly/a month or a year as continuous flow to the users, groups, projects etc. the user supports.

-add new rejuvenation of coins method: coins are transferred slowly over the timespan of 100 years back to the ocean, but spending them rejuvenates them esp. when they are transferred to very credible accounts. (con: people will use multiple accounts and transfer them without actually spending them to rejuvenate them)

-con of the system: users will spend money on real objects instead of keeping it in their account, but this also means that someone else will have that money.

-anti corruption task force with special privileges would be needed if all transactions are anonymous?
But also could be used to corrupt the system.

-Add: The All System is the combination of already existing technologies and ideas (IPFS, BITCON, ETHERIUM STEEM, DHT, Cryptocurrency, Smart Contracts, Web 3.0 ......) improving them and brining them together into one cooperative system. The aim is to build a system that creates a healthy competitive platform. Our current society gets less cooperative/supportive by the day and has been in an unhealthy competitive state for too long. I believe we have to change this in order to survive as a species. If we don't we are doomed to go extinct by or own hands and behavior.

-Add: Tests can't be only have/ask about one source of information. Leaders with opposing and differing views on the topic have to be elected and the test needs to have questions about all the different views, pros and cons. To ensure the optimum outcome of the vote.

-Unity through fracturing: Keeping ones culture and individuality uniting through coopertation.

-Simple Ledger that every node encrypts their own way. Because thousands of unique inhouse encryptions are harder to hack then one known open source encryption.

-The all system allows other systems to exists within groups but they are limited by the all systems base software and hardware.

-A digital currency that does not include the political side of currency will only further fuel the money wars. Currently every country/faction has their own currency. They work because they have politics, banks and the industry backing the currency. For a digital currency to work it either needs to be bound to a faction that has control over it OR it has to be approved by all factions. A currency that is not bound to any faction will be infiltrated and manipulated. If that is not possible it will be destroyed. The only way for a digital currency to work is by staying neutral. To stay neutral all factions need to be able maintain it. Meaning everyone needs to actively work on keeping it secure. That task cannot be done by trusting others to do it.

-I have yet to see a digital currency/stock besides my own that has any mechanism to resolve any kind of corruption that has breached its protection. They all use one unified security measure which is a huge security risk. If we take banks as an example they work like nodes in a crypto currency and every bank has their own security specialists and they use their own security measure. Relying on the userbase, an open ledger with anonymous users and open source code as secure is very naive. Open source is not a guarantee for security and an open ledger with anonymous users that need 0 credibility allows even a single user to write algorithms to manipulate the whole system unnoticed. Nobody is paid to keep the system corruption free those that are highly invested in that currency will only do work that is in their interest. If the system has flaws they will do everyhing to hide them. The majority of users lack the knowledge and capacity to find any manipulation attempts. From that low amount of users that truly understand the system most will keep flaws to themself and try to use them to their own advantage. Any Cyber Security specialist will tell that securing a system is something that is constantly changing, challenging and that nothing is 100% safe. Any digital currency that relies on "the community will find manipulation attempts" will only end up as a silently manipulated currency. There is no hardening (Cyber Sec term) method that guarantees a 100% safe system.

-A system can only be safe when maintained correctly. For that maintenence to work the system needs people that can be trusted. So far no digital currency except my own has presented any method to deal with trust. Random developers create a digital currency and the users need to rely on blind trust when they invest in those highly experimental systems.


.Descriptions

A shift in power by voting through others, creating a network of votes.

No more parties, no left or right. Only people that are doing the job they applied for and have been voted into by the majority.

It is time we end the age of greed and replace the leeches with leaders!

The All System strives to be like water, flowing everywhere and nourishing all life. The All-System has the power to create a fair society where a persons ideas and work are rewarded the right way. It enables people to follow their dreams and earn a living at the same time. While making sure tasks that nobody wants to do are still done.

Imagine a ball of Nanobots that either expunges parts of itself that have been corrupted or changes and implements/integrates the corruption into the ball.
That is how I imagine the system, it repairs itself and evolves while keeping its essence/core intact.
It can even change its essence/core if needed but only when every part of it is in unison about the change. The ball cares for every single one if itself and nourishes and keeps all parts healthy.

Every individual using the All-System is just a spark. By themselves they glow only slightly for an instant. They are only tiny sparks after all. But by gathering and supporting each other they shine as a sun!

The All System has no space for bottomless leeches. In the All System people are forced to become leaders in order to be wealthy (gain the support of many many individuals, not scam them).
Leeching from those that have too much works in nature. But leeches only take what they need.
Humans tend to become bottomless when money and power is involved. We do not have the luxury to feed bottomless leeches anymore. We need to change as a species or we will become extinct.

The system is actually really simple. In other words it's how we gain  jobs: We learn and gain knowledge, we prove ourselves and then are given money and responsibility. If we fail we stop earning that money and the responsibility is taken away.
The same applies for pretty much all instances of the all-system. Just in a way that is faster and more dynamic. Damage control can be easier applied and everyone can gain influence.