{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"thinker-ted-nelson","title":"Ted Nelson — Xanadu and the Dream of Connected Documents","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Ted Nelson — Xanadu and the Dream of Connected Documents**\n>\n> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# Ted Nelson — Xanadu and the Dream of Connected Documents\n\n## §SELF — thinker-ted-nelson\n\n**What this page is:** A profile of Ted Nelson, who coined the term \"hypertext,\" and his lifelong project Xanadu, which defined most of the features the World Wide Web still lacks.\n**What it explains:** Nelson's four key ideas — transclusion, bidirectional links, versioning, and micropayments — and why they were abandoned in favor of a simpler web.\n**Why read it:** To understand what the web could have been, what it actually is, and how modern systems can implement Nelson's original vision.\n\n### What Ted Nelson Is\n\nTed Nelson (born 1937) is an American sociologist and information technologist. He coined the word \"hypertext\" in 1963. \"Hypertext\" means text that contains links to other text, which a reader can follow to navigate between documents. Nelson also created Project Xanadu, a software system for connected documents that he began designing in 1960 and that continues in various forms today. Xanadu is the most ambitious hypertext system ever conceived — it includes features that the modern World Wide Web (invented by Tim Berners-Lee in 1989) does not have.\n\n### Why It Matters\n\nNelson proposed a web of documents where every quotation links back to its source, where links work in both directions, where nothing is ever deleted, and where creators are paid automatically when their work is quoted. The actual web implements none of these features. The web uses one-way links (page A links to page B, but page B does not know), no built-in versioning (when a page changes, the old version is usually lost), no automatic attribution for quotations, and no built-in payment system. The web won because it was simple — Berners-Lee designed it to be implementable in a few months. Xanadu was too complex to build with the technology available in the 1960s–80s. But Nelson's ideas remain relevant because the problems they solve (link rot, lost history, unattributed copying, lack of creator compensation) are major issues on the modern web.\n\n### The Key Idea\n\nNelson's central concept is that documents should be connected by reference, not by separation. In his model, a document is not a standalone file but a structure of connections to other documents. The four defining features of this model are:\n\n1. **Transclusion** (short for \"transclusive inclusion\"): When you quote a document, you do not copy the text. Instead, you insert a live link to the original. The quoted text appears in your document, but it is read from the source. If the source changes, your quotation updates automatically. This means there is only ever one copy of any piece of text — all quotations point to the same underlying data.\n2. **Bidirectional links**: Every link has a corresponding \"backlink.\" If page A links to page B, page B knows it is linked from page A. The reader of page B can see all pages that link to it. This is not how the web works — HTML (HyperText Markup Language, the format web pages are written in) defines one-way links only. The destination page has no automatic record of incoming links.\n3. **Versioning**: Every document keeps all previous versions. Nothing is ever overwritten or deleted. The system maintains a complete history of every change. This means a link to a document always points to a specific version, and old versions remain accessible.\n4. **Micropayments**: Every transclusion generates a small payment from the quoter to the quoted. If your document includes a transclusion from my document, you pay me a small amount automatically. This creates an economic model where creators are compensated when their work is referenced.\n\n### What He Got Right\n\n- **Links should be two-way.** One-way links create information asymmetry: the linking page knows where it points, but the target page does not know what points to it. Bidirectional links would enable readers to discover related content by following backlinks. They would also solve the \"link rot\" problem more visibly — if page B knows what links to it, it can notify those pages when it moves.\n- **Documents should preserve history.** The web's lack of built-in versioning means content disappears or changes without record. Scientific papers cite URLs that later break or point to different content. Legal references to web pages require archiving services because the original may change. Nelson's versioning model would prevent this.\n- **Quoting should be by reference, not by copy.** When you copy text, the copy diverges from the original. The original author updates their text, but your copy remains stale. When you transclude, the quotation stays synchronized. This is technically possible today — content delivery networks and embedded frames can display content from another source — but it is not a built-in feature of the web's architecture.\n\n### What He Got Wrong or Left Unfinished\n\n- **Xanadu was too complex to build.** Nelson's design required a centralized or federated system that tracked every document, every version, every link, and every transclusion globally. Building this with 1960s–80s technology proved impossible. The project went through multiple implementations (the most well-known was a version developed by Autodesk in the 1980s–90s) but none achieved the full vision. The web won because Berners-Lee reduced the problem to its minimum: one-way links, no versioning, no payments, no central registry. A graduate student could write a web server in a weekend. Xanadu required a team of engineers for years.\n- **Micropayments require economic infrastructure that did not exist.** Nelson's transclusion payments assumed a global micropayment system with low transaction fees. In the 1960s–80s, credit card processing cost too much per transaction for micropayments to be feasible. Digital payment systems (PayPal, 1998; Bitcoin, 2009) arrived decades later, but still do not integrate with document linking.\n- **Centralization vs. decentralization tension.** Xanadu's vision of tracking all links and transclusions globally implies a degree of centralization (a registry that knows about all documents). The web's decentralized design — anyone can host a page, no central registry needed — was key to its rapid growth. Nelson's model would require solving the technical and political problems of a global document registry.\n\n### How It Connects to Other Ideas\n\n- **The World Wide Web (Tim Berners-Lee, 1989).** The web is Nelson's hypertext idea with most of Nelson's features removed. Berners-Lee knew of Nelson's work and chose simplicity over completeness. The result was a system that could be built and deployed quickly but lacks bidirectional links, versioning, and transclusion. The web's success proves that a partial implementation of a good idea can beat a complete implementation that never ships.\n- **Hypertext as academic field.** Nelson's 1963 coinage of \"hypertext\" and his 1974 book *Computer Lib / Dream Machines* defined the conceptual space that later researchers (including Berners-Lee at CERN, and the developers of Apple's HyperCard in 1987) worked within. Nelson's ideas were widely discussed even when his software was not usable.\n- **OIP's repair linking and append-only ledger.** The Open Integrity Protocol (OIP) implements Nelson's bidirectional link idea through \"repair\" links: when a receipt fails verification, a repair_of link connects the repair receipt back to the failed receipt, and the failed receipt knows it has been repaired. OIP's append-only ledger (a database where new entries can be added but old entries cannot be deleted or modified) implements Nelson's versioning principle — nothing is ever lost. OIP's receipt graph (a network of interconnected verification records) creates transclusion-like reference chains where each receipt references the data it verifies.\n- **Content-addressed storage (IPFS, 2015).** The InterPlanetary File System stores data by its cryptographic hash — a mathematical fingerprint of the content. Retrieving data by its hash means the content is always the same (the hash would change if the content changed). This is a partial implementation of transclusion: you reference content by a unique identifier, and the identifier guarantees you get exactly that content. It does not support live updating (if the author changes the content, it gets a new hash), but it does guarantee that a reference always resolves to the same data.\n\n### Sources\n\n- Nelson, T. H. (1965). \"A File Structure for the Complex, the Changing, and the Indeterminate.\" *Proceedings of the 20th National Conference of the ACM*, 84–100.\n- Nelson, T. H. (1974). *Computer Lib / Dream Machines*. Self-published (later republished by Microsoft Press, 1987).\n- Nelson, T. H. (1981). *Literary Machines*. Self-published (multiple editions through 1993).\n- Berners-Lee, T. (1989). \"Information Management: A Proposal.\" CERN internal document.\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)\n- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)\n- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)\n- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)\n- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)\n- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)\n- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)\n- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/thinker-ted-nelson`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-ted-nelson`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Ted%20Nelson%20%E2%80%94%20Xanadu%20and%20the%20Dream%20of%20Connected%20Documents`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-ted-nelson"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-ted-nelson/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Thinkers (oip-thinkers). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":33,"label":"Thinkers on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:48.030Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"f7f5e44c30580686ac085076adfc29789976ea1e95b051f16a56300a76e81546"},{"ts":"2026-07-17T02:43:01.556Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-ted-nelson","response":"27 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"f7f5e44c30580686ac085076adfc29789976ea1e95b051f16a56300a76e81546","hash":"00782cc0f5969b3c0d8dec59fcce17ce1e1d8a9a8ae654ea8e3a4de454063ce9"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"00782cc0f5969b3c0d8dec59fcce17ce1e1d8a9a8ae654ea8e3a4de454063ce9"},"posted_at":"2026-07-15T04:20:48.030Z","created_at":"2026-07-15T04:20:48.030Z","updated_at":"2026-07-17T02:43:01.556Z","machine":{"shape":"article.machine/v1","slug":"thinker-ted-nelson","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-ted-nelson","json":"https://miscsubjects.com/api/articles/thinker-ted-nelson","bundle":"https://miscsubjects.com/api/articles/thinker-ted-nelson/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/thinker-ted-nelson/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-ted-nelson","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-ted-nelson\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-ted-nelson\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-ted-nelson/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"thinker-ted-nelson\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-ted-nelson | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-ted-nelson","json":"/api/articles/thinker-ted-nelson","markdown":"/api/articles/thinker-ted-nelson/bundle?format=markdown","skill":"/api/articles/thinker-ted-nelson/skill","topology":"/api/articles/thinker-ted-nelson/topology","versions":"/api/articles/thinker-ted-nelson/revisions","invocations":"/api/articles/thinker-ted-nelson/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-ted-nelson","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"f053664ddd5b8c76b0c275a273b3fb0150449ed7ee20a8263748d4ff9d47bb51","object":{"object_type":"article-object","identity":{"id":"article:thinker-ted-nelson","slug":"thinker-ted-nelson","title":"Ted Nelson — Xanadu and the Dream of Connected Documents"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/thinker-ted-nelson","role":"explain","audience":"human"},"skill":{"route":"/api/articles/thinker-ted-nelson/skill","role":"direct behavior","audience":"model","content":"---\nname: thinker-ted-nelson\ndescription: Apply the Ted Nelson — Xanadu and the Dream of Connected Documents article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Ted Nelson — Xanadu and the Dream of Connected Documents\n\nThis Skill is the behavioral expression of [the canonical article](/a/thinker-ted-nelson). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/thinker-ted-nelson.\n- Read claims and relationships at /api/articles/thinker-ted-nelson/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\n<!-- hierarchy:nav -- Path: OIP https://miscsubjects.com/a/oip › Thinker Reference https://miscsubjects.com/a/oip-thinker-reference › Thinkers https://miscsubjects.com/a/oip-thinkers › Ted Nelson — Xanadu and the Dream of Connected Document\n\n## Representations\n\n- Human: /a/thinker-ted-nelson\n- JSON: /api/articles/thinker-ted-nelson\n- Relationships: /api/articles/thinker-ted-nelson/topology\n- History: /api/articles/thinker-ted-nelson/revisions\n"},"json":{"route":"/api/articles/thinker-ted-nelson","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/thinker-ted-nelson/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: the owner or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: the owner says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.the owner.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/[OWNER_HANDLE]/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: the owner asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: the owner says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/[OWNER_HANDLE]/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: the owner asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: the owner asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: the owner says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: the owner says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: the owner asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: the owner says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-ted-nelson","thinker","ted","nelson"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/thinker-ted-nelson/invocations?status=success","failure_events":"/api/articles/thinker-ted-nelson/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"thinker-ted-nelson","title":"Ted Nelson — Xanadu and the Dream of Connected Documents","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Ted Nelson — Xanadu and the Dream of Connected Documents**\n>\n> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# Ted Nelson — Xanadu and the Dream of Connected Documents\n\n## §SELF — thinker-ted-nelson\n\n**What this page is:** A profile of Ted Nelson, who coined the term \"hypertext,\" and his lifelong project Xanadu, which defined most of the features the World Wide Web still lacks.\n**What it explains:** Nelson's four key ideas — transclusion, bidirectional links, versioning, and micropayments — and why they were abandoned in favor of a simpler web.\n**Why read it:** To understand what the web could have been, what it actually is, and how modern systems can implement Nelson's original vision.\n\n### What Ted Nelson Is\n\nTed Nelson (born 1937) is an American sociologist and information technologist. He coined the word \"hypertext\" in 1963. \"Hypertext\" means text that contains links to other text, which a reader can follow to navigate between documents. Nelson also created Project Xanadu, a software system for connected documents that he began designing in 1960 and that continues in various forms today. Xanadu is the most ambitious hypertext system ever conceived — it includes features that the modern World Wide Web (invented by Tim Berners-Lee in 1989) does not have.\n\n### Why It Matters\n\nNelson proposed a web of documents where every quotation links back to its source, where links work in both directions, where nothing is ever deleted, and where creators are paid automatically when their work is quoted. The actual web implements none of these features. The web uses one-way links (page A links to page B, but page B does not know), no built-in versioning (when a page changes, the old version is usually lost), no automatic attribution for quotations, and no built-in payment system. The web won because it was simple — Berners-Lee designed it to be implementable in a few months. Xanadu was too complex to build with the technology available in the 1960s–80s. But Nelson's ideas remain relevant because the problems they solve (link rot, lost history, unattributed copying, lack of creator compensation) are major issues on the modern web.\n\n### The Key Idea\n\nNelson's central concept is that documents should be connected by reference, not by separation. In his model, a document is not a standalone file but a structure of connections to other documents. The four defining features of this model are:\n\n1. **Transclusion** (short for \"transclusive inclusion\"): When you quote a document, you do not copy the text. Instead, you insert a live link to the original. The quoted text appears in your document, but it is read from the source. If the source changes, your quotation updates automatically. This means there is only ever one copy of any piece of text — all quotations point to the same underlying data.\n2. **Bidirectional links**: Every link has a corresponding \"backlink.\" If page A links to page B, page B knows it is linked from page A. The reader of page B can see all pages that link to it. This is not how the web works — HTML (HyperText Markup Language, the format web pages are written in) defines one-way links only. The destination page has no automatic record of incoming links.\n3. **Versioning**: Every document keeps all previous versions. Nothing is ever overwritten or deleted. The system maintains a complete history of every change. This means a link to a document always points to a specific version, and old versions remain accessible.\n4. **Micropayments**: Every transclusion generates a small payment from the quoter to the quoted. If your document includes a transclusion from my document, you pay me a small amount automatically. This creates an economic model where creators are compensated when their work is referenced.\n\n### What He Got Right\n\n- **Links should be two-way.** One-way links create information asymmetry: the linking page knows where it points, but the target page does not know what points to it. Bidirectional links would enable readers to discover related content by following backlinks. They would also solve the \"link rot\" problem more visibly — if page B knows what links to it, it can notify those pages when it moves.\n- **Documents should preserve history.** The web's lack of built-in versioning means content disappears or changes without record. Scientific papers cite URLs that later break or point to different content. Legal references to web pages require archiving services because the original may change. Nelson's versioning model would prevent this.\n- **Quoting should be by reference, not by copy.** When you copy text, the copy diverges from the original. The original author updates their text, but your copy remains stale. When you transclude, the quotation stays synchronized. This is technically possible today — content delivery networks and embedded frames can display content from another source — but it is not a built-in feature of the web's architecture.\n\n### What He Got Wrong or Left Unfinished\n\n- **Xanadu was too complex to build.** Nelson's design required a centralized or federated system that tracked every document, every version, every link, and every transclusion globally. Building this with 1960s–80s technology proved impossible. The project went through multiple implementations (the most well-known was a version developed by Autodesk in the 1980s–90s) but none achieved the full vision. The web won because Berners-Lee reduced the problem to its minimum: one-way links, no versioning, no payments, no central registry. A graduate student could write a web server in a weekend. Xanadu required a team of engineers for years.\n- **Micropayments require economic infrastructure that did not exist.** Nelson's transclusion payments assumed a global micropayment system with low transaction fees. In the 1960s–80s, credit card processing cost too much per transaction for micropayments to be feasible. Digital payment systems (PayPal, 1998; Bitcoin, 2009) arrived decades later, but still do not integrate with document linking.\n- **Centralization vs. decentralization tension.** Xanadu's vision of tracking all links and transclusions globally implies a degree of centralization (a registry that knows about all documents). The web's decentralized design — anyone can host a page, no central registry needed — was key to its rapid growth. Nelson's model would require solving the technical and political problems of a global document registry.\n\n### How It Connects to Other Ideas\n\n- **The World Wide Web (Tim Berners-Lee, 1989).** The web is Nelson's hypertext idea with most of Nelson's features removed. Berners-Lee knew of Nelson's work and chose simplicity over completeness. The result was a system that could be built and deployed quickly but lacks bidirectional links, versioning, and transclusion. The web's success proves that a partial implementation of a good idea can beat a complete implementation that never ships.\n- **Hypertext as academic field.** Nelson's 1963 coinage of \"hypertext\" and his 1974 book *Computer Lib / Dream Machines* defined the conceptual space that later researchers (including Berners-Lee at CERN, and the developers of Apple's HyperCard in 1987) worked within. Nelson's ideas were widely discussed even when his software was not usable.\n- **OIP's repair linking and append-only ledger.** The Open Integrity Protocol (OIP) implements Nelson's bidirectional link idea through \"repair\" links: when a receipt fails verification, a repair_of link connects the repair receipt back to the failed receipt, and the failed receipt knows it has been repaired. OIP's append-only ledger (a database where new entries can be added but old entries cannot be deleted or modified) implements Nelson's versioning principle — nothing is ever lost. OIP's receipt graph (a network of interconnected verification records) creates transclusion-like reference chains where each receipt references the data it verifies.\n- **Content-addressed storage (IPFS, 2015).** The InterPlanetary File System stores data by its cryptographic hash — a mathematical fingerprint of the content. Retrieving data by its hash means the content is always the same (the hash would change if the content changed). This is a partial implementation of transclusion: you reference content by a unique identifier, and the identifier guarantees you get exactly that content. It does not support live updating (if the author changes the content, it gets a new hash), but it does guarantee that a reference always resolves to the same data.\n\n### Sources\n\n- Nelson, T. H. (1965). \"A File Structure for the Complex, the Changing, and the Indeterminate.\" *Proceedings of the 20th National Conference of the ACM*, 84–100.\n- Nelson, T. H. (1974). *Computer Lib / Dream Machines*. Self-published (later republished by Microsoft Press, 1987).\n- Nelson, T. H. (1981). *Literary Machines*. Self-published (multiple editions through 1993).\n- Berners-Lee, T. (1989). \"Information Management: A Proposal.\" CERN internal document.\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)\n- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)\n- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)\n- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)\n- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)\n- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)\n- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)\n- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/thinker-ted-nelson`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-ted-nelson`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Ted%20Nelson%20%E2%80%94%20Xanadu%20and%20the%20Dream%20of%20Connected%20Documents`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-ted-nelson"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-ted-nelson/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Thinkers (oip-thinkers). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":33,"label":"Thinkers on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:48.030Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"f7f5e44c30580686ac085076adfc29789976ea1e95b051f16a56300a76e81546"},{"ts":"2026-07-17T02:43:01.556Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-ted-nelson","response":"27 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"f7f5e44c30580686ac085076adfc29789976ea1e95b051f16a56300a76e81546","hash":"00782cc0f5969b3c0d8dec59fcce17ce1e1d8a9a8ae654ea8e3a4de454063ce9"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"00782cc0f5969b3c0d8dec59fcce17ce1e1d8a9a8ae654ea8e3a4de454063ce9"},"posted_at":"2026-07-15T04:20:48.030Z","created_at":"2026-07-15T04:20:48.030Z","updated_at":"2026-07-17T02:43:01.556Z","machine":{"shape":"article.machine/v1","slug":"thinker-ted-nelson","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-ted-nelson","json":"https://miscsubjects.com/api/articles/thinker-ted-nelson","bundle":"https://miscsubjects.com/api/articles/thinker-ted-nelson/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/thinker-ted-nelson/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-ted-nelson","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-ted-nelson\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-ted-nelson\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-ted-nelson/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"thinker-ted-nelson\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-ted-nelson | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-ted-nelson","json":"/api/articles/thinker-ted-nelson","markdown":"/api/articles/thinker-ted-nelson/bundle?format=markdown","skill":"/api/articles/thinker-ted-nelson/skill","topology":"/api/articles/thinker-ted-nelson/topology","versions":"/api/articles/thinker-ted-nelson/revisions","invocations":"/api/articles/thinker-ted-nelson/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-ted-nelson","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"f053664ddd5b8c76b0c275a273b3fb0150449ed7ee20a8263748d4ff9d47bb51"}}}