Play tool
The Governance Memory System's itch.io pageResults
| Criteria | Rank | Score* | Raw Score |
| Overall | #1 | 4.400 | 4.400 |
Ranked from 5 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.
Leave a comment
Log in with itch.io to leave a comment.
Comments
i work in government (albeit a tiny one and would love to discuss this in more detail ) and it'd be extremely good for our use cases
instutional memory as a service ! dope
This is exactly the kind of conversation I want to have! Government is on the roadmap, but understanding the constraints early (privacy requirements, decision velocities, staff turnover every election cycle) shapes how I build this. Would love to learn what specific governance pain points you're dealing with. There might be something we can do together. DM me on Discord (@Othmangba) or email OCCResearch6@gmail.com.
This is a cool pitch! It rhymes with something I've been thinking about for Tollens - that a software project needs some kind of record for its historical quality decision making - "why did we do this and not that", version control for "why" not "what".
I didn't dig into the full technical details of what you are proposing, but I would love to see about more explanation of that "why" thinking here - since you are presenting architecture it is always useful for the audience if you include "why" in support of your "what"!
One other question that comes to mind as I read your pitch is "what organisations should use this, and what organisations should not?" - it seems at first glance a potentially quite heavyweight mechanism and I can imagine many kind of organisations where this level of administrative overhead is potentially not worth the value that a rigorous audit trail system could bring
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.
cool, sounds like you are already thinking about and have answers to the questions I am curious about!
> Each GMS layer maps directly to a failure mode observed in the research
this is the part I was intending to double click on! do you have some writing on this somewhere? sometikes an architecture goes from overwrought to elegant only once you take into account the problems you're trying to solve, and at other times some more elegant solution is possible to the same problems.
and it's great that you've thought about scaling path. do you have some validation with your ideal early adopter profile? if not that seems like important feedback to get early (I'm not connected at all with block chain folks so I don't really know what they think is valuable.)
I can send you the draft of the research paper I wrote to accompany this and/or a much more concise slide deck. And yeah, I'm currently piloting it on a popular blockchain. I received positive community feedback when proposing phase one for implementation on the forum, but they had other priorities to address within their governance initiative before I could propose it onchain. I will try to propose it within the next 2 weeks as things have finally settled down.
I enjoyed this pitch. I think there are a lot of opportunities for this within varying infrastructures, both blockchain and off chain.
Some blockchain partners you may want to look into are bonfires.ai. That guy is super cool and working on knowledge graph agents. Let me know and I can get you connected to him on telegram
I also see some potential overlap between these mechanisms and the Virts platform, although we'd have to find ways to sew the frankenstein together haha. Regardless, I think projects like this are great for improving the landscape and epistemics of the field
Yeah, it would be awesome to get connected with him. I just looked into their stuff. It definitely feeds into a few layers of my system. My telegram is @othmangba. I also left a comment on your post to further connect.
Great concept. I think it would be neat to have an LLM agent personality that's basically inhabiting the "spirit" of a company, acting on the behalf of their interests. Ever so slightly (or significantly) dystopian sci fi, as well, but what can you do - probably highly profitable. I'm still planning on looking over the files you sent me -- I wouldn't mind helping a bit with some implementation, I'm just busy right now
Thanks for the feedback. The personality angle is quite interesting. I do see it being helpful when it ties to a research organization or company, but a singular personality in a more decentralized context may be harder to execute. The ecosystems have a mission, vision, and values you can base personality on, but the "how to" of achieving them becomes a point of contention (based on my personal experience). Definitely still worth exploring. Thanks again for looking over the files. I'd like to see if there are any glaring liabilities I haven't thought through. No rush when it comes to helping with the implementation, I'm patient.