Maggie Appleton 写设计、人类学和智能体界面时，习惯先画清楚隐喻，再谈工具。把「The Pattern Language of Project Xanadu」整理成可阅读的中文笔记：问题在哪、界面默认会把人带去哪、落地时该改什么。原站导航、评论回响和广告已去掉。
Architectural Pattern Languages
When it comes to visionary, before-its-time software, it’s hard to find a better archetype than Ted Nelson’s Project Xanadu .
It’s infamous in the technology community as a sixty-year project that never quite launched. A cautionary tale of what happens when you overhype, underdeliver, and try to stuff an operating system’s worth of features into a single piece of proprietary software. The kind of tale that makes our ferociously lean startup culture of Move Fast, Break Things, and Demo or Die seem almost sensible.
A Pattern Language
Xanadu was a hypothetical hypertext system. The word hypothetical is a bit strong. Many versions were built. There is a working demo showcasing a few of its features here . But there is no active version on the App Store or Product Hunt I can link you to.
It’s hard to read the word hypertext in 2021 5ya and not believe its synonymous with the system Tim Berners-Lee built in 1989 37ya – the World Wide Web that became so much more than linked text on digital screens. The version of hypertext you are reading this on is the only hypertext most of us have ever known.
Xanadu as a Design Pattern
And yet the idea of hypertext predates Berners-Lee by two decades. The term was coined in 1963 63ya by none other than Ted Nelson as part of a much larger vision; one small brick in the grand Xanadu dream mansion. While Nelson coined the word, the notion of linked documents goes back to Jorge Luis Borges The Garden of Forking Paths” in 1941 85ya and Vannevar Bush’s Memex machine in 1945 81ya – both significant, named influences for Nelson.
To talk about Xanadu, we need to put a pin in our current understanding of hypertext . Our preconceived notions of what a link is, how it works, and what digital text is capable of threatens to overwrite the alternate history we’re about to explore.
The Patterns
Ted hoped Xanadu would be a medium for “ serious electronic literature ” – a paradigm shift that would free us from the material constraints of paper. His vision was the first to meaningfully consider how storing information in digital bits could reconfigure the way we read, write, cite, and share words.
Xanadu’s failure to mature into a widespread, useable commercial product is great fodder a dramatic cover story . One fuelled by the noticeably combative language in Xanadu’s documentation :
1. Visible Links
“The computer world is a continual war over software politics and paradigms” where “we fight on” for “vindication” and “the last laugh.”
One feels like the dinner guest who has stumbled into a raging marital argument over unwashed tea towels. You don’t dare ask for context.
2. Parallel Documents
Yet these historical skirmishes and financial flops are also the least interesting thing about Xanadu. The most interesting part is its Pattern Language .
Pattern Languages are sets of flexible, reusable solutions to common design problems.
值得单独记下的观察
- How do we structure information and build relationships between pieces of data that help us see them across contexts, and clarify understanding?
- How do we build systems that allow people to collaborate on shared documents without losing authorship? How do we credit and compensate authors based on their contributions?
- How do we bring ideas and data from a variety of sources into conversation with our own, while leaving a clear trail back to the origin?
- Transclusion and Transcopyright Dreams
- A Short History of Bi-Directional Links
落地时建议先做的 5 件事
- 先写清这个工具在强化思考还是在替人思考。
- 默认交互不要只会谄媚：该追问、该给反例、该要求证据。
- 智能体界面要露出推理步骤，而不是只给一个光滑答案。
- 知识发布用可生长的笔记，而不是一次性营销长文。
- 改产品前先画隐喻：用户以为自己在做什么，系统实际在做什么。
和智能体产品怎么接
龙虾PRO做 OpenClaw 落地时，最该从这类笔记里拿走的是「别把聊天框当唯一界面」。数字员工要能追问、能验证、能把过程摊开，而不是只负责说好话。
本文侧重全链路风控方法论。落地时请用自身业务单据做回放验证，不要把示例阈值直接当生产策略。 相关：风控体检 · 方案资源
常见问题 FAQ
Project Xanadu 是什么？它跟现在的网页有什么区别？
Project Xanadu 是泰德·尼尔森在上世纪60年代提出的一个超文本系统构想，比我们现在用的万维网早得多。它设想的是一个更复杂、更“严肃”的电子文献系统，比如支持永久可见的双向链接和文档的平行对照阅读，而现在的网页链接通常是单向且容易失效的。它更像是一个未完成的、宏大的思想实验。
为什么 Xanadu 被称为技术界的“警示故事”？
因为它是一个持续了六十年、备受期待却从未真正完成的项目。文章指出，它的教训在于：过度吹嘘、交付不足，并试图把一个操作系统级别的庞大功能塞进一个专有软件里。这种“想得太多、做得太慢、范围失控”的模式，在当今追求快速迭代的创业文化中显得格格不入，所以常被用来警示后来者。
文中提到的“模式语言”具体指什么？
“模式语言”指的是 Xanadu 项目中提出的一套灵活、可复用的设计方案集合，用来解决信息结构设计中的常见问题。例如，如何让文档间的引用关系一目了然（可见链接），如何让不同版本的文档并行显示以便比较（平行文档）。它是一套关于如何设计超文本系统的可借鉴的“解决方案模板”。
“可见链接”和“平行文档”这两个模式想解决什么问题？
“可见链接”模式是为了解决在现有网络中，链接指向容易丢失或失效的问题，它要求链接关系在界面上清晰可见、双向且永久。“平行文档”模式则是为了让引用者和被引用者的文档能够并排显示，方便读者直接对照上下文阅读。这两个模式都旨在增强信息的可追溯性、关联性和阅读深度。
Xanadu 的这些设计模式，对我们今天构建系统有什么启示？
文章结尾的“落地建议”部分指出，我们可以先从借鉴这些模式的核心思想开始。比如，在我们的工具或内容系统中，优先思考如何让知识间的引用关系更透明、更稳固，或者如何让不同来源的观点在同一空间内对话。这有助于我们设计出信息层次更清晰、协作更顺畅的产品，而不是简单复制链接功能。
根据笔记，落地时最先该做什么？
文章在最后给出了“落地时建议先做的5件事”，但没有列出具体内容。不过从上下文推断，第一步很可能是：先放下对现有超文本（即网页链接）的固有认知，像文章说的那样“为当前理解打个暂停”，重新审视“链接”和“数字文本”的本质可能性，从 Xanadu 提出的基础问题（如如何清晰地建立信息关系）开始思考。