garden.ooo:当完成概念松动,网重新成为网
garden.ooo: When the Concept of Completion Loosens, the Web Becomes a Web Again
橋本麦(Baku Hashimoto)是一位活跃在东京的视觉艺术家,以生成艺术、运动图形和实验影像闻名——戛纳铜狮、Ars Electronica 入选、东京TDC 大奖。但他过去两年在做的事情,与这些奖项所命名的实践全然不同。他在建造一套叫做 garden.ooo 的内容管理系统:Local-First、基于 Wiki 结构、拒绝层级分类、拒绝时间线、拒绝"已完成"与"未完成"的二元对立。这个 CMS 不是他的"作品"——它是他的网站本身运行的基础设施,是他通过 dogfooding 逐步生长出来的东西。
garden.ooo 对今日 Web 进行了三次凿构操作。第一凿:CMS 的层级构——WordPress 以降的内容管理系统以投稿类型(post type)、分类目录(category)、标签树为构,要求你在写作之前就搭好盒子。当你遇到一个"既是作品又是事件"的页面时,这套盒子就破裂了。garden.ooo 凿掉了所有分类体系,只留下链接。页面与标签不加区分,结构不是被预设的,而是从链接之间涌现的。这是万维网最初被提姆·伯纳斯-李构想时的样子——根茎状的、任何人可以向任何地方伸出链接的网。这个网的网眼结构,是被 CMS 的层级构凿掉之后暴露出的余项。
第二凿:云优先构——Notion、Medium、Google Docs,你的数据住在别人的服务器上,便利是拿控制权交换的。garden.ooo 凿掉了对云的依赖。所有数据以本地文本文件为唯一真相源(Single Source of Truth),云只是镜像。实现上是三层结构:本地 Markdown 文件 ↔ 浏览器 IndexedDB(RxDB)↔ 远程 MongoDB。你甚至不用注册账号就可以开始使用。数据格式与 Obsidian 兼容——纯 Markdown 加 YAML frontmatter——意味着你可以用记事本、Obsidian、Cursor 乃至 sed 来编辑你的网站。纯文本文件是凿掉所有专有格式之后的余项:最古老、最持久、最普适的数字信息载体。
第三凿,也是最深的一凿:完成概念构。今日的发布系统维持着一个二元对立——"已发布"(打磨完毕的、正式的、不可更改的)与"未发布"(草稿、私密的、不存在的)。garden.ooo 将这个二元凿成了一个梯度。它用四级可见性(public / unlisted / protected / private)和 permanent 标记,把内容的成熟度比喻为物态变化:气体(碎碎念)→ 液体(非晶态的思考)→ 结晶(存档)。它的设计原则之一叫做"ダダ漏れ"——"漏",允许不同完成度的内容自由混居。另一个原则叫"愚行权"——约翰·斯图尔特·密尔的概念——系统承认用户发布不完美内容的权利,CMS 不管你的页面是否杂乱。被凿掉的是"完成"这个概念本身;余项是那个巨大的、在已发布和未发布之间的灰色地带——人类思想真正居住的地方,但所有现有发布系统都没有为它留出空间。橋本自己写道:完成概念をガバガバにする——松动完成的概念。这恰恰是余项之美的核心宣言。
命名的缺口极宽:它不是 CMS(没有层级、没有投稿类型),不是 Wiki(它做的是作品集、日记、付费内容),不是静态网站生成器(有动态同步和数据库层),不是 Obsidian(面向公开 Web 发布),不是博客(拒绝时间线),不是数字花园工具(更全面——有复制同步、付费内容、多级可见性)。橋本把它的名字本身做成了URL——garden.ooo 既是系统名也是服务名。它的前身叫 Morion。思想系谱上溯至 Ted Nelson 的 Xanadu、Zettelkasten、梅棹忠夫的京大式卡片、Cosense(前 Scrapbox)的不区分页面与标签的设计、Obsidian 的本地优先、Olia Lialina 的 Vernacular Web。但没有一个前辈能完整命名它——因为 garden.ooo 试图同时还原网的本来面目,并且为"泄漏"和"愚行"提供基础设施。
现在看到它尤其重要,因为它正处在余项的状态。garden.ooo 仍在通过橋本自己的网站 dogfooding 生长,设计原则已写就但实现仍在推进。它还没有正式对外发布。这个系统的逻辑尚未凝固为构——它本身还是余项。一旦它被命名为"某种类型的工具"并被广泛采用,它就会成为新的已构。现在,在它还在松动完成概念的时候,是它最活着的时刻。
baku89.com/garden ↗Baku Hashimoto is a visual artist based in Tokyo, known for generative art, motion graphics, and experimental film — Cannes Lions Bronze, Ars Electronica selection, Tokyo TDC Grand Prize. But what he has been building for the past two years is something entirely different from the practice those awards name. He has been constructing a content management system called garden.ooo: Local-First, wiki-structured, rejecting hierarchy, rejecting timelines, rejecting the binary opposition between "finished" and "unfinished." This CMS is not his "work" — it is the infrastructure on which his own website runs, something grown incrementally through dogfooding.
garden.ooo performs three chisel operations on today's web. The first chisel targets the CMS hierarchy-construct. Content management systems since WordPress demand that you build boxes before you write: post types, categories, tag trees. The moment a page is "both a work and an event," the box system collapses. garden.ooo chisels away all classification, leaving only links. Pages and tags are not distinguished; structure is not preset but emerges from links between things. This is how the World Wide Web was originally imagined by Tim Berners-Lee — rhizomatic, where anyone can link to anywhere. The mesh topology of that original web is the remainder exposed after the CMS hierarchy-construct is chiseled away.
The second chisel targets the cloud-first construct. Notion, Medium, Google Docs — your data lives on someone else's server, convenience traded for control. garden.ooo chisels away cloud dependency. All data is stored locally as text files, the Single Source of Truth; the cloud is merely a mirror. The implementation is three-layered: local Markdown files ↔ browser IndexedDB (RxDB) ↔ remote MongoDB. You can start using it without even creating an account. The data format is Obsidian-compatible — plain Markdown plus YAML frontmatter — meaning your site can be edited in Notepad, Obsidian, Cursor, or sed. The plain text file is the remainder after all proprietary formats have been chiseled away: the oldest, most durable, most universal vessel for digital information.
The third and deepest chisel targets the completion-construct. Today's publishing systems maintain a binary: "published" (polished, official, immutable) versus "unpublished" (draft, private, nonexistent). garden.ooo chisels this binary into a gradient. Using four visibility levels (public / unlisted / protected / private) and a "permanent" flag, it treats content maturity as a phase transition: gas (fragments, tweets) → liquid (amorphous thought) → crystal (archive). One of its design principles is called "dada-more" (—) — literally "leaking overflow" — allowing content of different maturity levels to coexist freely. Another principle is "gukou-ken" — Mill's concept of the right to foolishness — the system acknowledges the user's right to publish imperfect content; the CMS does not police whether your pages are messy. What is chiseled away is the concept of completion itself; the remainder is that vast grey zone between published and unpublished — where human thought actually lives, but for which no existing publishing system has made room. Hashimoto himself writes: loosen the concept of completion. This is, precisely, the core declaration of the beauty of the remainder.
The naming gap is wide open. It is not a CMS (no hierarchy, no post types). Not a wiki (it serves as portfolio, diary, paid content platform). Not a static site generator (it has dynamic sync and database layers). Not Obsidian (it is designed for public-facing web publishing). Not a blog (it rejects timeline structure). Not a digital garden tool (it is more comprehensive — with replication, paid content, graduated visibility). Hashimoto made the name itself into a URL — garden.ooo is both the system name and the service name. Its predecessor was called Morion. Its intellectual lineage traces to Ted Nelson's Xanadu, Zettelkasten, Tadao Umesao's Kyoto-style index cards, Cosense's (formerly Scrapbox) refusal to distinguish pages from tags, Obsidian's local-first principle, and Olia Lialina's Vernacular Web. But no single predecessor can fully name it — because garden.ooo attempts to simultaneously restore the web's original mesh topology and provide infrastructure for "leaking" and "foolishness."
Seeing it now matters more than later, because it is currently in the state of remainder. garden.ooo is still growing through Hashimoto's own site via dogfooding; the design principles are documented but the implementation continues to advance. It has not yet been formally released to the public. The system's logic has not yet solidified into construct — it is itself still remainder. Once it is named as "a type of tool" and widely adopted, it will become new construct. Right now, while it is still loosening the concept of completion, is when it is most alive.
baku89.com/garden ↗