公共物品：Mycelium Protocol 的数字公共物品，一个视频讲一个开源组件

谁做的

这条线里的每一个组件，都出自 MushroomDAO——Mycelium Protocol 的治理组织。

Mycelium Protocol 是一个去中心化协作网络，使命是「构建让合作更快、更多样的去中心化协作网络」，而数字公共物品（Digital Commons）是它的立身之本：协议层的一切产出默认开源、免费、无许可。MushroomDAO 负责把这件事组织起来——研发公共物品、维护社区国库、引导需要的社区用上协议。

所以这条线不是「某个团队顺手开源了几个工具」，而是一个协议组织的核心产出被逐个讲清楚。

什么是数字公共物品

一句话：开源、免费、无许可，任何人都可以使用、修改和部署。

数字公共物品有个和商业平台完全相反的性质——它不会因为用的人变多而让每个人分到的变少。一份开源代码被一万个人用，和被十个人用，对第十个人的体验没有任何损害；而一个商业平台的用户越多，通常意味着广告越多、数据被挖得越深、议价能力越弱。

我们拒绝以提取个人隐私数据为基础的商业模式，也拒绝构建数字劳工生态。所以我们做出来的东西，默认是公共物品。

这条线讲什么

一期一个组件，每期回答同样几个问题：

它解决什么痛点——对应🧠 痛点地图上的哪一条，不是「我们想做」而是「这里确实卡住了」
为什么是自己做的——🔬 技术实验那边已经开盒过现成方案，说明为什么它们不够用
怎么装、怎么跑——从零到能用的完整过程，包括在什么硬件上跑得动
怎么改、怎么拼——组件是组件，不是产品；讲清楚它的接口，以及怎么和别的组件组合
数据在哪——local-first 是默认设定：敏感数据不出你的硬件边界，哪些走远程会说清楚

为什么都是「组件」而不是「产品」

因为产品会假设你要按它设计的方式工作，组件不会。

一个完整产品意味着一整套预设——你的数据存在哪、你的流程长什么样、你能不能换掉其中一块。组件把这些选择还给你：喜欢哪块用哪块，不喜欢的换掉，全都不喜欢就只拿走接口定义自己写。

代价是需要你多花一点力气去拼。收益是没有任何一块是你换不掉的，也就没有任何一块能锁住你。

收费吗

核心组件对个人和小社区永久免费，这是协议层的承诺，不是限时优惠。

MushroomDAO 确实有对应的商业实体做企业定制和托管服务，但那是另一件事——开源的那份不会因此被阉割或延迟发布。Mycelium Protocol 的双生模型（开源组织做公共物品、商业收入按固定比例回流由 Gnosis Safe 多签管理的社区国库、全链上透明）写在 Mycelium 的使命文档里，公开可查。

和另外两条线的关系

这条线是另外两条的出口：🧠 问题思考确认了真问题，🔬 技术实验验证了现成方案不够，那么缺的那块由我们补上，然后开源出去。

Who Builds These

Every component in this line comes from MushroomDAO — the governing organization of Mycelium Protocol.

Mycelium Protocol is a decentralized collaboration network whose mission is to “make cooperation faster and more diverse,” and digital commons are what it stands on: everything the protocol layer produces is open source, free, and permissionless by default. MushroomDAO is what organizes that work — building the public goods, maintaining the community treasury, and helping communities actually adopt the protocol.

So this line isn’t “some team open-sourced a few tools on the side.” It’s a protocol organization’s core output, explained one piece at a time.

What a Digital Public Good Is

In one line: open source, free, permissionless — anyone may use, modify, and deploy it.

Digital public goods have a property that runs exactly opposite to commercial platforms: more users doesn’t mean less for each user. Open-source code used by ten thousand people is no worse for the tenth person than code used by ten. A commercial platform with more users usually means more ads, deeper data extraction, and less bargaining power for you.

We reject business models built on extracting personal data, and we reject building a digital-labor ecosystem. So what we build is a public good by default.

What This Line Covers

One component per episode, answering the same set of questions each time:

What pain it solves — which entry on the 🧠 Pain Point Map it maps to; not “we felt like building it” but “people are genuinely stuck here”
Why we built it ourselves — the 🔬 Tech Experiments line already tore down the existing options, so we explain why they fell short
How to install and run it — the full path from zero to working, including what hardware it actually runs on
How to modify and compose it — a component is a component, not a product; we document the interfaces and how it combines with others
Where your data lives — local-first is the default: sensitive data stays inside your hardware boundary, and anything that goes remote is stated plainly

Why Components, Not Products

Because a product assumes you’ll work the way it was designed. A component doesn’t.

A finished product carries a whole set of presets — where your data lives, what your workflow looks like, whether you’re allowed to swap out any single piece. Components hand those choices back: take the parts you like, replace the ones you don’t, and if you like none of them, take just the interface definitions and write your own.

The cost is a bit more assembly on your side. The payoff is that no piece is un-swappable, which means no piece can lock you in.

Is Any of It Paid

Core components are free forever for individuals and small communities. That’s a protocol-level commitment, not a limited-time promotion.

MushroomDAO does run a matching commercial entity for enterprise customization and hosting, but that’s a separate matter — the open-source version doesn’t get crippled or delayed because of it. Mycelium Protocol’s dual model (an open-source organization producing public goods, with a fixed share of commercial revenue flowing back to a Gnosis Safe multisig community treasury, fully transparent on-chain) is documented publicly in Mycelium’s mission docs.

How It Relates to the Other Two Lines

This line is the outlet for the other two: 🧠 Problem Thinking confirms a real problem, 🔬 Tech Experiments shows the existing options fall short — so we build the missing piece and open-source it.