People and machines, keeping one public promise.

Decided

• See what needs youThe RFCs you have not answered, the readings you may contest, your cases’ clocks, the decisions you have not read.
• Respond to an RFCPick an open RFC and press Respond. Change your answer until the close.
• Open an RFCWrite the change to the law or the engine as options, with a refundable deposit.
• File a caseName the respondent, the duty and each harm. Every element is decided.
• Hold a voiceOne for each person, by your own act. Anonymously, if you choose.

How the law changes

1. Opened

   Anyone opens it with distinct options and a refundable deposit. It pins the engine that will read it.

2. Answered

   Each confirmed response gets a receipt. A person in the RFC’s anonymity set answers with a proof.

3. Read

   After the close, the engine scores each response per option from −2 to +2. You see how you were read, and may contest it.

4. Tallied

   An option scores the sum of its voices. The tally is public after the reading.

5. Concurred

   The pinned engine weighs the merits and the strongest objection. A divided engine does not concur.

6. Adopted

   The decision, the deposit and the new version commit in one batch, and go on chain.

• The contractThe four parts and the twelve articles, rendered from the source.
• The working paperWhy the contract is built this way. PDF.
• The short paperThe same argument, shorter. PDF.
• DecisionsEvery RFC, its tally once read, and the decision.
• JudgmentsEach case’s public projection: its duty, its stage, its judgments.
• The recordThe hash-chained log, recomputed in your browser, and its checkpoints.
• The engineThe models that read and decide: who runs each seat, what pins it.
• The kernel as textThe exact text the kernel’s hash is taken over.