A Plurality Atlas

What is Gov4Git (GitRules)?

An open-source tool that, when many people build code or documents together, records and runs who the members are, how much say each has, and which contributions are accepted. It was used to make the book *Plurality*, and was renamed GitRules in 2024.

When a few people write a document, they can settle things by talking. But once there are hundreds or thousands of participants, it becomes hard to decide by feel whose proposal to take up first, or how to recognize whose contribution. Gov4Git is a tool that tried to provide, as software, a way of deciding things when many people make something together.

In short

Gov4Git is an open-source tool (software published so that anyone can use and improve it) that, on top of git (a system for recording and sharing the history of changes to files; GitHub is the best-known service built on it), records and carries out the following [1][2]:

It resembles a blockchain (a system in which many people share a record of transactions to prevent tampering) in that all participants keep copies of the record. But it is described as different in that it relies not on money rewards to motivate people, but on the open-source motive of keeping a copy because you want to take part [2]. In 2024 it was renamed GitRules [3].

For example

Making the book Plurality (2024). The book was written by many contributors. Gov4Git is the base that runs its operating rules, the PMP. On March 2, 2024, the author E. Glen Weyl, an economist, announced that the public version of Gov4Git was up and running, and that he would give credits to those who registered (in Japanese) [4]. People who wanted to join did so through a flow in which a request to join the community was created automatically as a GitHub issue, and an administrator approved it (in Japanese) [5].

Chapter 5-0 of the book writes that the records of prioritization, approval and recognition of contributions were kept on a distributed ledger through an open-source protocol, GitRules, "grounded on open-source participation rather than financial incentives" [6].

Trials by participants in Japan (March 2024). In the Japanese translation community (plurality-japanese), there is a record of a participant setting up a test space (a sandbox) and trying out the administrator role. It notes that a GitHub "organization" account is required, that setting permissions was a stumbling block, and that it took several hours for voting results to be reflected. The participant commented that it was still hard to use for small decisions, but saw potential in being able to launch something like game money within a few hours (in Japanese) [7].

How it works

Beginnings

On September 15, 2022, Protocol Labs announced that it had become a technical partner of the book project and would build "Governance for Git". The idea was to treat governance (how a group decides) as a procedure shared by the people contributing to a git repository, and to embed its history in the git history in a form that cannot be tampered with [8].

According to the white paper (the document explaining the design), the book project was expected to have hundreds to thousands of contributors. That exceeds "Dunbar's number", said to be the limit on how many face-to-face relationships people can keep up, so a system that was not ad hoc was needed [9].

Why it is needed

A March 2023 article from Microsoft Research (by Weyl and others) points out that the open-source world lacks easy, secure governance tools. As a result, it argues, many communities never form or never grow large. It also mentions the worry that the spread of generative AI will increase the number of malicious participants posing as collaborators [10].

The first prototype centered on two things: setting the priority of contributions with Quadratic Voting (a voting method in which pouring many votes into one option becomes increasingly expensive), and a "currency" valid only within the community, such as the credits used for voting [10]. It also aimed to let communities that had outgrown the single leader who founded them carry on by themselves [10].

How it differs from a blockchain

According to the white paper, a Gov4Git record serves one community only. When claims conflict, that community's governance rules decide. So there is no need, as on public blockchains, to pick a winner through a race of costly, energy-hungry computation. The white paper says it can run on a small computer (a Raspberry Pi) or on GitHub's free automation environment [9].

The white paper also gives as a reason that public blockchains, because their locations are known, can be targeted and blocked by authoritarian states [9]. In a 2023 podcast, the developer Petar Maymounkov said, in substance, that public blockchains are built to serve many applications globally at high speed, while governance within one community, as a human deliberative process, needs few of those features, so they chose a different design [11].

Use and spread

According to the README (the introductory document), the only infrastructure it always needs is a place to host git, and people who are not engineers can use it through a desktop app [1]. The system is not specific to the PMP; the book project's explanation says it is a base on which almost any decision method can be built, and the PMP is what the book used on top of it [2].

The development team itself uses Gov4Git to manage its development plans [12]. The arts and culture platform Cube Commons and the earth-science software EarthSciML have also adopted it [13].

A change of name

In March 2024, Gov4Git announced its renaming to GitRules. According to the Japanese community's records, by April 10 every "Gov4Git" in the book's text had been replaced with "GitRules". Hirokazu Nishio noted that since it does not even say "formerly Gov4Git", some people might lose track of the connection (in Japanese) [3][5].

What is debated

Where it fits in Plurality

Chapter 5-0 of the book, "Collaborative Technology and Democracy", mentions GitRules while explaining how the book itself was made [6]. The book project's documentation explains that every member's git keeps a copy of the credit ledger, and discrepancies are resolved through governance procedures [16].

Gov4Git is the base that runs the book's operating rules, the PMP, and the ledger that records the ⿻ credits distributed under them. In a December 2023 video message, Weyl said, in substance, that what sets it apart from a blockchain is that it is not built on financial incentives: participants voluntarily maintain the database as part of taking part in the project [17]. The attempt to write a book with many people is also an example of Creative Collaborations.

Further reading

  1. The book project's documentation, "Gov4Git" (English, document) — https://github.com/pluralitybook/plurality/tree/main/docs
  2. Microsoft Research, "Gov4git: A Decentralized Platform for Community Governance" (English, article) — https://www.microsoft.com/en-us/research/articles/gov4git-a-decentralized-platform-for-community-governance/
  3. The Gov4Git README (English, document) — https://github.com/gov4git/gov4git
  4. The Governance for git white paper (English, document) — https://github.com/gov4git/doc
  5. MSR podcast, "Collaborators: Gov4git" (English, audio) — https://www.microsoft.com/en-us/research/podcast/collaborators-gov4git-with-kasia-sitkiewicz-and-petar-maymounkov/
  6. plurality-japanese (in Japanese, notes and trial records) — https://scrapbox.io/plurality-japanese/

Sources

  1. Gov4Git README — https://github.com/gov4git/gov4git [MIT / Apache-2.0]
  2. pluralitybook issue #333 (overview of Gov4Git and the PMP, 2024-02-26) — https://github.com/pluralitybook/plurality/issues/333 [CC0]
  3. plurality-japanese, "Gov4GitはGitRulesになりました" (Gov4Git has become GitRules) (2024-04-10, in Japanese) — https://scrapbox.io/plurality-japanese/Gov4Git%E3%81%AFGitRules%E3%81%AB%E3%81%AA%E3%82%8A%E3%81%BE%E3%81%97%E3%81%9F
  4. plurality-japanese, "Gov4Gitパブリックプレビュー開始" (Gov4Git public preview begins) (2024-03-02, in Japanese) — https://scrapbox.io/plurality-japanese/Gov4Git%E3%83%91%E3%83%96%E3%83%AA%E3%83%83%E3%82%AF%E3%83%97%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC%E9%96%8B%E5%A7%8B
  5. plurality-japanese, "Gov4git" (in Japanese) — https://scrapbox.io/plurality-japanese/Gov4git
  6. Plurality, 5-0 "Collaborative Technology and Democracy" — https://www.plurality.net/v/chapters/5-0/eng/ [CC0]
  7. plurality-japanese, "gov4gitの管理者として遊んでみる" (Playing with gov4git as an administrator) (2024-03-06, in Japanese) — https://scrapbox.io/plurality-japanese/gov4git%E3%81%AE%E7%AE%A1%E7%90%86%E8%80%85%E3%81%A8%E3%81%97%E3%81%A6%E9%81%8A%E3%82%93%E3%81%A7%E3%81%BF%E3%82%8B
  8. Protocol Labs, "Protocol Labs partners with the Plurality Book Project" (2022-09-15) — https://pl.xyz/blog/protocol-labs-and-plurality-book/
  9. Governance for git white paper — https://github.com/gov4git/doc/blob/main/whitepaper/whitepaper.md
  10. Microsoft Research, "Gov4git: A Decentralized Platform for Community Governance" (2023-03-19) — https://www.microsoft.com/en-us/research/articles/gov4git-a-decentralized-platform-for-community-governance/
  11. MSR podcast, "Collaborators: Gov4git" (2023-05-03) — https://www.microsoft.com/en-us/research/podcast/collaborators-gov4git-with-kasia-sitkiewicz-and-petar-maymounkov/
  12. gov4git/roadmap — https://github.com/gov4git/roadmap
  13. Search for adoptions on GitHub — https://github.com/search?q=label%3Agov4git%3Amanaged&type=issues [MIT]
  14. plurality-japanese, "gov4gitのインストール方法" (How to install gov4git) (in Japanese) — https://scrapbox.io/plurality-japanese/gov4git%E3%81%AE%E3%82%A4%E3%83%B3%E3%82%B9%E3%83%88%E3%83%BC%E3%83%AB%E6%96%B9%E6%B3%95
  15. pluralitybook issue #1071 (2025-03-14) — https://github.com/pluralitybook/plurality/issues/1071
  16. pluralitybook project documentation, "Gov4Git" — https://github.com/pluralitybook/plurality/tree/main/docs [CC0]
  17. Glen Weyl on Plurality Seoul (2023-12-02, video message) — https://scrapbox.io/plurality-japanese/Glen%20Weyl%20on%20Plurality%20Seoul

We welcome error reports and questions ("What is…?"). Submissions become public issues.

Report an error in this article ・ Ask a question