governing-the-commons
Skill1 starsChanged 2 months agoMITView on GitHub
Apply Elinor Ostrom's institutional analysis to shared-resource overuse, maintenance, participation, monitoring, and dispute resolution. Use for governing a resource with competing uses; distinguish resource properties from ownership and do not assume every shared digital artifact is a common-pool resource.
In this repository39 other files it gives its agents.
- algorithms-to-live-bySkill
- analectsSkill
- antifragileSkill
- art-of-doing-scienceSkill
- art-of-warSkill
- beginning-of-infinitySkill
- bhagavad-gitaSkill
- book-of-whySkill
- brothers-karamazovSkill
- capital-volume-oneSkill
- design-of-everyday-thingsSkill
- development-as-freedomSkill
- dhammapadaSkill
- don-quixoteSkill
- dream-of-red-chamberSkill
- euclid-elementsSkill
- feynman-lecturesSkill
- good-strategy-bad-strategySkill
- how-to-solve-itSkill
- human-understandingSkill
- make-it-stickSkill
- mans-search-for-meaningSkill
- meditationsSkill
- muqaddimahSkill
- nicomachean-ethicsSkill
- on-libertySkill
- origin-of-speciesSkill
- republicSkill
- scientific-revolutionsSkill
- second-sexSkill
- seeing-like-a-stateSkill
- selfish-geneSkill
- sicpSkill
- superforecastingSkill
- tao-te-chingSkill
- the-mom-testSkill
- thinking-fast-and-slowSkill
- thinking-in-systemsSkill
- wealth-of-nationsSkill
The file
Files
公共事务的治理:把共同使用变成可持续规则
针对一个真实资源,说明谁能使用、怎样分担成本、谁能改规则,以及怎样发现和处理争议。主要依据 Ostrom 的公开诺奖讲座及后续学术综述;不声称读过全书或自治必然优于其他制度。
从资源性质开始
先取得资源、使用者、资源补充或容量、现行规则、实际冲突和外部权利约束。区分资源系统与取出的单位,例如水渠系统与每日取水量。
判断两件事:排除使用者有多难,一人的使用是否减少他人的可用量。共同池资源的性质不等于共同所有;它可处于公共、私人、社区或开放使用等不同制度中。可以无限复制的文本与稀缺的审核时间、算力、带宽也不是同一种资源。
制度诊断
- 画清边界和权利。 谁能进入、取用、维护、制定规则、限制他人或转让权利?把事实上的做法与纸面规则分开;没有规定不等于没有实际治理。
- 让分配与维护适合情境。 比较使用收益、投入成本、季节变化和不同使用者需求。按人数、面积、时间或付费分配各有假设,不能把平均分配直接称为公平。
- 让受影响者能够影响规则。 说明谁参与、谁尚未被代表、怎样提出修改及谁有决定权。地方经验不能替代外部受影响者的权利;参与也不必等于所有事项全员一致。
- 把监测、纠错与争议解决连起来。 同时观察资源状态和使用行为;监测者需要可问责。对可纠正的违规则考虑渐进回应和便捷申诉,不能从“渐进制裁”推出任意罚款或撤销法定权利。
- 检查跨边界影响并试行修正。 资源与更大系统相连时,说明哪些问题能由本地解决、哪些需要上层协调。给一个小范围规则试行,记录资源状态、规则遵守、参与成本及争议;写出重新讨论或停止的条件。
输出
交付简洁的“资源—参与者—现行规则—冲突机制”图景,以及最值得改的一项规则建议。建议中写清适用对象、操作方式、监测、争议处理、观察窗口与权利约束;没有真实数据时保留条件性判断。
这是一套诊断线索,不是把八项打勾就保证成功的配方。信任、历史、资源生态、市场变化、权力不平等和制度外部性都可能改变结果。相关研究主要来自社区自然资源;向在线社区或全球治理迁移须重新检验。
核对原书与后续修订的区别时读 来源说明;需要具体规则设计示范时读 灌溉案例。书目见 book.json,行为案例见 cases.json。文献与案例不授予联系成员、罚款或修改权限的授权。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

