A “User” is any individual person with an account registered with Clyste.
A "Member" is a User that has been verified by the community and whose account is not suspended.
A “Guest” is a User that has not been verified.
A “Representative Officer” or “RO” is a Member that has been elected by the Member community to a Representative Officer Position.
A “Delegate” is a User that has been appointed to a Delegate Position by an RO.
“Voting Rights” consist of the ability to create Problems, endorse Proposals in the first stage and vote on the acceptance of Proposals in the third stage.
Every Member shall receive Voting Rights.
Verification shall be done by the Representative Officer for Administration or any Delegates who have been tasked to assist in verification.
All Users have the ability to interact with the platform in any way that is not restricted to another role.
Every Member shall receive shares representing an ownership stake in Clyste upon account verification.
The number of shares each Member receives is dependant on rules set by Projects overseen by the Finance Representative Officer.
Users may be punished for violations of the community standards by Delegates that have been tasked to do so upon recognition of a violation.
Users will be informed of the reason for the punishment upon enforcement of the community standards.
Punishments may include: removal or restriction of content, temporary or permanent suspension of a User, restriction or abridgement of a User’s ability to post.
A Member that has been punished is allowed three chances in a 365 day period, starting from the date of enforcement, to file for and receive a review of the punishment decision.
If, after the review, the punishment decision is deemed to be invalid, the punishment will be rescinded.
"Problems" are statements relating issues that Members have with Clyste
A Problem may be “Endorsed” once by any Member.
Problems may be created by Members, and must be assigned to a Representative Officer position.
Problems shall be made visible for all Users to see and for Members to comment on.
Problems can be resolved in the following ways:
“Proposals” are possible solutions to a single Problem.
The “Creator” of a Proposal is granted special rights and responsibilities over the Proposal.
Any Member may create a Proposal in response to a Problem.
Proposals must progress through three stages before becoming a Project.
The Creator may, at any time, cancel the Proposal process and delete the Proposal.
In the first stage, the Proposal must describe a possible solution to the Problem and garner 100 Endorsements from Members in order to progress to the second stage.
The Creator may invite and remove “Collaborators”.
Collaborators are permitted to edit the body of the Proposal.
In the second stage, the Proposal is open for the Creator and Collaborators to edit the body of the Proposal. The Creator may also set a crowdfunding target at this time.
The Creator may, at any time, progress a Proposal in the second stage to the third stage.
Members may, at any time during the second and third stages, Donate to the project.
If a Proposal is cancelled all Donations are returned to each contributor.
In the third stage, the Proposal may no longer be altered in any way.
A Proposal in the third stage will be available for all Members to vote on for 7 days from the time it was advanced to that stage.
A Proposal may be given either a vote for approval or a vote for disapproval by any Member with voting rights.
A Proposal requires a quorum of votes, equal to 25% of the total number of Active Members, in order to be eligible to become Approved.
A Proposal that has reached the end of the voting period without progressing into a Project is demoted back to the second stage.
If the Creator has set a crowdfunding target and the total value of donations is less than the target at the end of the third stage, the Proposal is demoted to the second stage regardless of the outcome of the vote.
A Proposal requires more than 66% of its votes for approval in order to progress into a Project In Review.
A “Project” is the plan and the execution of the solution outlined in a Proposal and consists of a set of “Tickets” and a “Deadline” for Completion.
A “Ticket” is a single item of work with an associated “Reward”.
Tickets can be “Credited” to individual Members or groups of Members.
Tickets are to be created by the Representative Officer assigned to the originating Problem or by any Delegate with the power to do so.
A Project is “Completed” when all of its Tickets have been Credited and the Representative Officer assigned to the originating Problem or any Delegate with the power to do so ends the Project.
If a Project reaches its Deadline without being Completed then the Project is considered to be “Canceled”.
A Canceled Project has ended and is frozen and cannot be changed or interacted with in any way, the reason for why the Project was Canceled will be made available for all Members for review.
A Project is considered a “Project In Review” until the RO Assigned to the originating Problem votes on the Project.
The RO assigned to the originating Problem may vote to “Accept” the Project, “Reject” the Project or “Request Amendments” to the Project.
If the RO assigned to the originating Problem votes to “Reject” or to “Request Amendments” then they must also supply their reasoning for their decision.
If the RO assigned to the originating Problem votes to Reject a Project, the Project is Canceled.
If the RO assigned to the originating Problem votes to Request Amendments to a Project, the Project will revert back to the state it was in right before the Proposal that created it progressed to the third stage; The Proposal will also include the reasoning made by the RO for their decision visible on the Proposal.
A Project begins when an Accepted Project In Review has been given a Deadline and at least one Ticket by the Representative Officer assigned to the originating Problem or any Delegate with the power to do so.
Projects are to be funded via donations received in the Proposal stage or by funds made available to the Representative Officer assigned to the originating Problem from the Clyste budget.
Upon completion of a task outlined by a Ticket, the Representative Officer assigned to the originating Problem or any Delegate with the power to do so, may Credit the Ticket to the Member or Group of Members that have completed the task.
Project funds are to be disbursed upon Project Completion in accordance with the associated Rewards for each Ticket to those who have been Credited with each Ticket.
The current status of the Project, its Deadlines, its Tickets, the Submissions to its Tickets, and who those Tickets are Credited to is to be available for all Members to review.
“Initiatives” are Proposals for time-limited changes to the platform.
Projects that result from Initiatives must be implemented over the course of six days, and any changes made as a result will be reverted seven days after the Project ends.
Initiatives may be created by any Member at any time.
Initiatives are created as Proposals in the third stage all requirements and Delegate Positions must be defined by the creator at the time of creation.
Initiatives are chosen by a week long “Initiative Selection”
Initiative Selections begin on Monday in the time zone of the location that Clyste is headquartered in and last for 162 hours.
Initiatives have the same quorum requirements as a Proposal in the third stage.
Initiatives are scored by taking the votes for the Initiative, subtracting the votes against the Initiative and multiplying the resultant value by the total number of votes divided by the quorum requirement of votes.
The Initiative with the highest positive score at the end of the Initiative Selection progresses to the next stage.
A Project In Review created from an Initiative must be reviewed by the Representative Officer responsible for Initiatives within 6 hours of the end of the Selection. If the Representative Officer Rejects the Project In Review, the Initiative with the next highest score progresses into a Project In Review.
If the Representative Officer Accepts the Project In Review, The deadline for the Project is set to 144 hours from the Monday after the Initiative Selection ends.
An “Election” is a single race wherein Members choose a Member to be Elected to a Representative Officer Position.
An Election must be held under the following circumstances:
Elections are to be conducted over the course of 28 24-hour days divided into 4 7-day weeks.
The Election will begin when an Election “Problem” is created.
During the first week of the Election, Members who are not Delegates may create “Nomination” Proposals to the Election Problem.
Nomination Proposals may not be Donated to nor may they have crowdfunding targets set.
Nomination Proposals require 5% of the total number of Members to Endorse them before it may progress into the second stage.
Nomination Proposals that are still in the first stage at the end of the first week of the Election are to be forcibly closed.
During the second week of the Election, Members who are the Creator of a Nomination Proposal may progress that Proposal from the second stage to the third stage.
Nomination Proposals in the third stage may be voted on for the second and third week of the Election.
Nomination Proposals do not require the Representative Officer assigned to the Problem to vote in approval to progress.
Nomination Proposals require a quorum of 33% of the total number of Members in order to pass.
Nomination Proposals in the third stage are to be given a score by adding the number of votes for approval and subtracting the number of votes for disapproval and multiplying the resultant value by the total number of votes divided by the number of votes required for quorum.
Beginning on the third week, Nomination Proposals are to be automatically closed if the score for that Proposal is in the bottom 25th percentile for that election.
If no Nomination Proposal is in the bottom 25th percentile and there are more than two Proposals, the Nomination Proposal with the lowest score is to be automatically closed
At the end of the third week, if no Nomination Proposal has fulfilled the quorum requirement, then a Nomination Proposal for the current Representative Officer progresses into a Transition Project.
At the end of the third week, the Nomination Proposal with the highest score progresses into a Transition Project.
If there is a tie, the Nomination Proposal with the lowest number of total votes wins
if there is still a tie, The Election is extended for a single day.
The Election may be extended for a number of days no greater than the number of remaining days in the Election.
If a Transition Project has not started by the end of the fourth week, the Nomination Proposal to progress into a Transition Project is to be selected randomly.
A Deadline of a Transition Project is automatically set to be the end of the fourth week of the Election.
A Transition Project has a two Tickets, and no additional Tickets may be added,
The first Ticket is to select the “Representative Officer-elect” and is to be Credited to the Creator of the Nomination Proposal that has progressed into the Transition Project when the Transition Project is created.
The second Ticket transfers the title of Representative Officer and, and is to be automatically Credited to the Representative Officer-elect immediately before the deadline of the Project.
Representative Officers are to appoint Delegates to Delegate Positions created by Projects that arise from Problems assigned to their Representative Officer Position.
Representative Officers are to oversee the actions of Delegates and to enforce the community guidelines upon them.
Representative Officers are responsible for planning and executing Projects.
Representative Officers must set Deadlines and create Tickets for all Approved Proposals that originate from Problems assigned to them in a timely manner.
Representative Officers are required to ensure that the requirements for the platform that have been outlined in this document are enforced.
Representatives may voluntarily step down, in this case, they may select an “Interim Representative Officer” from one of their delegates. If they do not choose an “Interim Representative Officer,” the other Representative Officers may choose one via a committee vote.
If a Representative Officer steps down, an Election will immediately begin for the Representative Officer Position.
During an Election the Interim Representative Officer will fulfill all responsibilities of the Position and after the election concludes the Interim Representative Officer will return to being a Delegate.
Representative Officers may be removed by a vote from a Representative Officer Committee. The Committee must attain a majority of votes and at least 50% of the number of Representatives.
There shall be one Representative Officer Position for each of the following Categories with the associated scopes and responsibilities:
Administration: User Verification, Platform Moderation, setting community guidelines and the constitution.
Product: Frontend / Backend development, code and open source maintenance.
Design: UI/UX Frontend Design, processes and workflows.
Growth: User Acquisition, SEO, PR, and arranging deals with external organizations.
Legal: Creating legal documents, Terms of service, compliance with governmental requests and regulations.
Finance: Budget, Accounts / Managing and Disbursing funds within the platform.
Strategy: Goal setting, Assessing whether Projects are successful, Initiatives.
Any meeting with at least 75% of the total number of Representative Officers present can be made into a “Representative Officer Committee”.
Representative Officer Committees can be formed to make decisions to ensure compliance of the platform with this document.
Representative Officer Committees must make a record of the meeting including the Representative Officers in attendance, any decisions made and the reasons why available to the Members for review. If there is information that cannot be revealed to the Members due to security or legal concerns, then 30% of the Adjudication Committee will be randomly selected to review the meeting and any decisions made for compliance with this document.
If a majority of the selected Adjudication Committee Delegates find the meeting or any decisions made therein to be non-compliant, then the decisions are reverted.
A Member Elected to a Representative Officer Position shall serve for 365 days starting from the day after the last day of the Election.
A “Delegate Position” is a position within the platform that is given a predefined set of responsibilities and the power to execute those responsibilities.
The responsibilities and powers granted to a Delegate Position are to be defined within a Proposal. When this Proposal becomes a Project the Delegate Position is created and at the end of the Project the Delegate Position is removed.
A “Delegate” is a Member that has been appointed to a Delegate Position.
A Delegate may not currently be a Representative Officer nor serve in more than one Delegate Position at any given time.
A Delegate inherits all the responsibilities and powers of the Delegate Position for the period in time that they remain in the Delegate Position.
A Representative Officer or any Delegate with the power to do so may appoint a Member to a Delegate Position that is not currently being held by a Delegate.
A Representative Officer or any Delegate with the power to do so may remove a Delegate from a Delegate Position at any time.
Delegate Positions may be granted the unique power to remove Members from Clyste (but not Representative Officers or Delegates), who have violated the rules outlined in the Community Guidelines, Terms Of Service, or this document.
Delegate Positions may be granted the ability to view privileged information that may not be seen by Members due to policies that are outlined in the Terms Of Service or this document.
Delegate Positions may be granted the ability to be assigned to a Project. When assigned to a Project, the Delegate Position has also granted the same authority over the Project as the Representative Officer.
Being assigned to a Project allows a Delegate Position to make Tickets for that Project, set the Deadline for that Project and Credit Tickets to Users for that Project.
Delegate Positions may change the platform within boundaries set by the Proposal that created them, if no boundaries are set then the Delegate Position may not enact changes.
A Delegate can perform any action that they have the power to perform in order to fulfill the responsibilities of the Delegate Position they hold.
The “Adjudication Committee” is responsible for reviewing disciplinary decisions upon an Appeal as well as reviewing decisions made during Representative Officer Committee meetings.
“Adjudication Committee Positions” are special Delegate Positions that are tied to this document and cannot be created or removed except by the procedures outlined in this document.
The Adjudication Committee will consist of a panel of 5 Delegate Positions with an additional two members added for every 100,000 Members.
Adjudication Committee Positions may be granted to a Delegate for one year. At the end of the year, the Adjudication Committee Position will be revoked.
The Adjudication Committee’s Delegate Positions can be granted to Members by a majority vote by a Representative Officer Committee.
Delegates will be granted access to all information that may be relevant to a decision that they are tasked with making.
Appeals will be randomly assigned to three Delegates on the Adjudication Committee and will vote to either overturn or accept the disciplinary decision. If a majority of the assigned Delegates vote to overturn a disciplinary action, the status of the Member will be returned to the state it was in before the disciplinary action was enacted.
The Representative Officer, or any Delegate that has been assigned to a Project or with the power to do so, may remove any Delegate that has been given a Delegate Position within the Project.
Clyste issues two types of “Tokens”:
A “Stable Token” whose value is always equal to $0.02 US
A “Premier Token” whose value is equal to a proportion of the value of the Platform at the current time.
The number and Price of Premier tokens available for purchase will be determined by the rules set by Projects overseen by the Finance Representative Officer.
Premier Tokens may only be exchanged with Clyste for Stable Tokens
Clyste offers its Members direct rewards for tasks completed in the form of Stable Tokens.
Clyste will offer holders of Premier Tokens an option to exchange them for Clyste shares upon Clyste’s IPO.
Until the IPO, Premier Tokens will serve as substitutes for share ownership.
Dividends will be disbursed to from Clyste’s quarterly Profits to its shareholders.
Clyste shall make all materials related to the proper functioning of all systems in use available for any Member to examine in full.
Clyste is to create and make available for all Members to audit accurate budgetary and financial statements
Clyste is to disclose all contracts and any legal documents that impose legally binding restrictions on Clyste’s operations.
In cases where the content of materials cannot be disclosed due to conflicts with the law or with the community guidelines, those items do not need to be made available; however, knowledge of the existence of, the reasons why they are exempted, and number of such materials must be made available.
Any personal information pertaining to any Members is also exempt from disclosure requirements.
This document may be changed only through Projects originating as Problems assigned to the Administration Representative Officer.
A Proposal intending to suggest a change to the constitution must include the entirety of this document including the suggested changes.
The Administration Representative Officer must, while Proposal is in its third stage, flag the Proposal as a “Constitutional Amendment”.
A Project that results from a Proposal that has been flagged as a Constitutional Amendment is then permitted to change the text of this document to the copy of the document included with the Proposal.
No other changes may be made, and the new constitution is in effect as soon as the Project closes.
A Proposal that has been flagged as a Constitutional Amendment requires a Quorum of at least 75% of the total number of Members with Voting Rights.
The Administration Representative Officer is not required to vote in approval of Proposal flagged as a Constitutional Amendment in order for it to pass.
A vote of disapproval by the Administration Representative Officer does not automatically close the Proposal.
In order to provide stability to the organization during the early stages of its existence as a platform, the election process is thus amended for the first 10 years after the enforcement of this document.
Elections may only be held for Representative Officer Positions that have had at least one Election.
No Elections shall be held for any Representative Officer Position during the first year after this document is enacted.
In the event that a Representative Officer who is not eligible for an Election steps down or is removed from office, their successor shall be chosen by the Strategy Representative Officer.
At the end of each year, a Representative Officer Committee must be formed to select at least one Representative Officer to be immediately put up for Election. This Committee must be formed by the end of the first month of the next year; If no committee has been formed, then every Representative Officer will be automatically put up for Election.