itch.io

Good questions. This system I'm building IS version control for an organization's governance.  I'm so happy you made that connection. On the 'why': governance gets treated like a fire extinguisher, ignored and overlooked until a crisis arises. The case studies, in the research paper I wrote backing this solution (Juno's panic-driven token confiscation, Gitcoin's slow attention decay, NEAR's procedural ambiguity during transition), all share the same root cause: no structured memory between decision cycles. Contributors rotate out, taking institutional knowledge with them. New decision-makers inherit authority without knowing why past choices were made. Each GMS layer maps directly to a failure mode observed in the research.

On which organizations should use it: GMS is modular by design. The Governance Health Index diagnoses which dimensions are weak, and organizations only adopt the layers that address those weaknesses. A lightweight org might only need proposal metadata and outcome reviews. They don't have to run the full stack. The system is both diagnostic and prescriptive. The scaling path has three tiers: Stage 1 is blockchain protocols (transparent data, fast cycles, high stakes). Stage 2 is digital communities and cooperatives (housing co-ops, mutual aid networks, platform governance). Stage 3 is traditional institutions (municipal bodies, civic organizations, academic departments). Each tier introduces new constraints, especially around privacy, but the core governance primitives (proposals, votes, delegation, outcomes, power concentration) transfer across all of them.