{"_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-roy-fielding","title":"Roy Fielding — The Man Who Named How the Web Works","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) › **Roy Fielding — The Man Who Named How the Web Works**\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# Roy Fielding — The Man Who Named How the Web Works\n\n## §SELF — thinker-roy-fielding\n\n**What this page is:** A profile of the computer scientist who described the architectural style that makes the World Wide Web scalable.\n**What it explains:** REST (Representational State Transfer), its six constraints, and why its most important feature — HATEOAS — failed until large language models appeared.\n**Why read it:** You will understand why the web works the way it does, why REST APIs are not actually RESTful, and why the full vision of REST is only now becoming possible.\n\n### What Roy Fielding Did\n\nRoy Fielding is a computer scientist who earned his Ph.D. at the University of California, Irvine, in 2000. His doctoral dissertation, \"Architectural Styles and the Design of Network-based Software Architectures,\" identified and named the set of constraints that make the World Wide Web work. He did not invent the web itself — Tim Berners-Lee did that in 1989. Fielding gave a name to the pattern Berners-Lee had built, and showed why that pattern scales.\n\n### The Key Idea: REST\n\nREST stands for Representational State Transfer. It is an architectural style, not a technology or a protocol. An architectural style is a set of constraints placed on how a system is built. Fielding identified six constraints that define REST:\n\n1. **Client-server separation.** The user interface (client) and data storage (server) are separate. They communicate across a network. This lets each evolve independently.\n2. **Statelessness.** Each request from client to server must contain all information needed to understand and process it. The server stores no session state about the client. This means any server can handle any request, which makes load balancing trivial.\n3. **Cacheability.** Responses must explicitly label themselves as cacheable or not. A cache is a temporary store of data. When a response is cacheable, a client or intermediate server can reuse it later without asking the origin server again. This reduces load and improves speed.\n4. **Layered system.** A client cannot tell whether it is connected directly to the end server or to an intermediate (a proxy, a gateway, a load balancer). Layers can be added, removed, or changed without the client knowing.\n5. **Uniform interface.** All resources are identified the same way, manipulated through the same operations, and described with the same message format. On the web, this means URLs identify resources, HTTP methods (GET, POST, PUT, DELETE) manipulate them, and responses carry representations (usually HTML or JSON).\n6. **Hypermedia as the Engine of Application State (HATEOAS).** This is the constraint most people ignore. It means that every response from the server contains not just data, but also links to the actions the client can take next. The client does not need to know the URL structure in advance. It discovers what to do by reading the links in each response.\n\n### What REST Got Right\n\nThe web scaled to billions of users because of these constraints. Statelessness meant a server could crash and another could take over without anyone noticing. Cacheability meant content could be served from edges of the network, close to users, instead of from a central point. The layered system meant proxies, CDNs (Content Delivery Networks), and firewalls could be inserted without breaking anything. The uniform interface meant any browser could talk to any server.\n\n### What REST Got Wrong or Left Unfinished\n\nHATEOAS never worked in practice. Fielding's dissertation Chapter 5 — the section on hypermedia — is the most important part, but it was almost entirely ignored for two decades.\n\nThe problem: HATEOAS requires the client to *understand* the links in each response. A link is only useful if the client knows what clicking it means. For example, a response contains a link with the label \"add-to-cart.\" A human reading HTML understands what that means. But a computer program reading a JSON API response sees a URL and a string. It does not know what \"add-to-cart\" means unless a programmer hard-coded that knowledge into it.\n\nEvery REST API client ever built was \"dumb code that could not read.\" Programmers had to write documentation saying \"this link does X,\" and then write code that encoded that same knowledge. The client could not discover what to do next by reading the response. It had to be told in advance.\n\nThis meant HATEOAS was reduced to a decorative feature — links included in API responses that no client actually used to navigate.\n\n### Why This Is Changing Now\n\nA large language model (LLM) is a computer program trained on vast amounts of text. It can read natural language and infer meaning. An LLM reading a response that contains a link labeled \"add-to-cart\" understands what that link does, because it has seen that phrase and its usage patterns in its training data.\n\nThe LLM is the first client that can actually read and understand HATEOAS links. It does not need a programmer to hard-code the meaning of every link. It can discover the API's structure by reading the responses, the same way a human discovers a website by reading the links on each page.\n\nThis is what Fielding described in 2000. It just needed a reader that could do the reading.\n\n### How It Connects to Other Ideas\n\n- **Object Interface Protocol (OIP):** OIP defines how objects communicate across systems. REST's HATEOAS constraint, combined with an LLM as the client, means OIP endpoints can describe themselves. An LLM-driven agent can read an OIP endpoint's hypermedia response and understand what operations are available without prior documentation.\n- **Semantic Web:** Tim Berners-Lee's vision of machines traversing linked data graphs also failed for the same reason — no machine could *understand* what it was traversing. LLMs solve that problem too.\n- **Capability security:** Mark Miller's work on capability-based systems (possession conveys authority) aligns with REST's statelessness — each request carries its own credentials, just as each capability reference carries its own authority.\n\n### Sources\n\n- Fielding, Roy Thomas. \"Architectural Styles and the Design of Network-based Software Architectures.\" Ph.D. dissertation, University of California, Irvine, 2000. Chapter 5 covers REST.\n- Fielding's blog posts clarifying REST vs. HTTP APIs (2008), available via the Internet Archive.\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-roy-fielding`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-roy-fielding`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Roy%20Fielding%20%E2%80%94%20The%20Man%20Who%20Named%20How%20the%20Web%20Works`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-roy-fielding"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-roy-fielding/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:45.806Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"36d2ffbf9f434b0bc395bcaae4c492b97efd7b19e3d909f0f565cdefce591c48"},{"ts":"2026-07-17T02:42:58.697Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-roy-fielding","response":"32 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"36d2ffbf9f434b0bc395bcaae4c492b97efd7b19e3d909f0f565cdefce591c48","hash":"2facfb6f75004a11ad67a8d89b360b470f433c1139e92a2f474dd5711f1eb80a"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"2facfb6f75004a11ad67a8d89b360b470f433c1139e92a2f474dd5711f1eb80a"},"posted_at":"2026-07-15T04:20:45.806Z","created_at":"2026-07-15T04:20:45.806Z","updated_at":"2026-07-17T02:42:58.697Z","machine":{"shape":"article.machine/v1","slug":"thinker-roy-fielding","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-roy-fielding","json":"https://miscsubjects.com/api/articles/thinker-roy-fielding","bundle":"https://miscsubjects.com/api/articles/thinker-roy-fielding/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-roy-fielding/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-roy-fielding","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-roy-fielding\",\"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-roy-fielding\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-roy-fielding/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-roy-fielding\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-roy-fielding | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-roy-fielding","json":"/api/articles/thinker-roy-fielding","markdown":"/api/articles/thinker-roy-fielding/bundle?format=markdown","skill":"/api/articles/thinker-roy-fielding/skill","topology":"/api/articles/thinker-roy-fielding/topology","versions":"/api/articles/thinker-roy-fielding/revisions","invocations":"/api/articles/thinker-roy-fielding/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-roy-fielding","ok":false,"issues":[{"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":"c2d8b2da20e53d7ac4065a3117e3bdda7e18382ad7d04018621139cff6a426d2","object":{"object_type":"article-object","identity":{"id":"article:thinker-roy-fielding","slug":"thinker-roy-fielding","title":"Roy Fielding — The Man Who Named How the Web Works"},"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-roy-fielding","role":"explain","audience":"human"},"skill":{"route":"/api/articles/thinker-roy-fielding/skill","role":"direct behavior","audience":"model","content":"---\nname: thinker-roy-fielding\ndescription: Apply the Roy Fielding — The Man Who Named How the Web Works article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Roy Fielding — The Man Who Named How the Web Works\n\nThis Skill is the behavioral expression of [the canonical article](/a/thinker-roy-fielding). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/thinker-roy-fielding.\n- Read claims and relationships at /api/articles/thinker-roy-fielding/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 › Roy Fielding — The Man Who Named How the Web Works Shel\n\n## Representations\n\n- Human: /a/thinker-roy-fielding\n- JSON: /api/articles/thinker-roy-fielding\n- Relationships: /api/articles/thinker-roy-fielding/topology\n- History: /api/articles/thinker-roy-fielding/revisions\n"},"json":{"route":"/api/articles/thinker-roy-fielding","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/thinker-roy-fielding/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-roy-fielding","thinker","roy","fielding"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/thinker-roy-fielding/invocations?status=success","failure_events":"/api/articles/thinker-roy-fielding/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-roy-fielding","title":"Roy Fielding — The Man Who Named How the Web Works","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) › **Roy Fielding — The Man Who Named How the Web Works**\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# Roy Fielding — The Man Who Named How the Web Works\n\n## §SELF — thinker-roy-fielding\n\n**What this page is:** A profile of the computer scientist who described the architectural style that makes the World Wide Web scalable.\n**What it explains:** REST (Representational State Transfer), its six constraints, and why its most important feature — HATEOAS — failed until large language models appeared.\n**Why read it:** You will understand why the web works the way it does, why REST APIs are not actually RESTful, and why the full vision of REST is only now becoming possible.\n\n### What Roy Fielding Did\n\nRoy Fielding is a computer scientist who earned his Ph.D. at the University of California, Irvine, in 2000. His doctoral dissertation, \"Architectural Styles and the Design of Network-based Software Architectures,\" identified and named the set of constraints that make the World Wide Web work. He did not invent the web itself — Tim Berners-Lee did that in 1989. Fielding gave a name to the pattern Berners-Lee had built, and showed why that pattern scales.\n\n### The Key Idea: REST\n\nREST stands for Representational State Transfer. It is an architectural style, not a technology or a protocol. An architectural style is a set of constraints placed on how a system is built. Fielding identified six constraints that define REST:\n\n1. **Client-server separation.** The user interface (client) and data storage (server) are separate. They communicate across a network. This lets each evolve independently.\n2. **Statelessness.** Each request from client to server must contain all information needed to understand and process it. The server stores no session state about the client. This means any server can handle any request, which makes load balancing trivial.\n3. **Cacheability.** Responses must explicitly label themselves as cacheable or not. A cache is a temporary store of data. When a response is cacheable, a client or intermediate server can reuse it later without asking the origin server again. This reduces load and improves speed.\n4. **Layered system.** A client cannot tell whether it is connected directly to the end server or to an intermediate (a proxy, a gateway, a load balancer). Layers can be added, removed, or changed without the client knowing.\n5. **Uniform interface.** All resources are identified the same way, manipulated through the same operations, and described with the same message format. On the web, this means URLs identify resources, HTTP methods (GET, POST, PUT, DELETE) manipulate them, and responses carry representations (usually HTML or JSON).\n6. **Hypermedia as the Engine of Application State (HATEOAS).** This is the constraint most people ignore. It means that every response from the server contains not just data, but also links to the actions the client can take next. The client does not need to know the URL structure in advance. It discovers what to do by reading the links in each response.\n\n### What REST Got Right\n\nThe web scaled to billions of users because of these constraints. Statelessness meant a server could crash and another could take over without anyone noticing. Cacheability meant content could be served from edges of the network, close to users, instead of from a central point. The layered system meant proxies, CDNs (Content Delivery Networks), and firewalls could be inserted without breaking anything. The uniform interface meant any browser could talk to any server.\n\n### What REST Got Wrong or Left Unfinished\n\nHATEOAS never worked in practice. Fielding's dissertation Chapter 5 — the section on hypermedia — is the most important part, but it was almost entirely ignored for two decades.\n\nThe problem: HATEOAS requires the client to *understand* the links in each response. A link is only useful if the client knows what clicking it means. For example, a response contains a link with the label \"add-to-cart.\" A human reading HTML understands what that means. But a computer program reading a JSON API response sees a URL and a string. It does not know what \"add-to-cart\" means unless a programmer hard-coded that knowledge into it.\n\nEvery REST API client ever built was \"dumb code that could not read.\" Programmers had to write documentation saying \"this link does X,\" and then write code that encoded that same knowledge. The client could not discover what to do next by reading the response. It had to be told in advance.\n\nThis meant HATEOAS was reduced to a decorative feature — links included in API responses that no client actually used to navigate.\n\n### Why This Is Changing Now\n\nA large language model (LLM) is a computer program trained on vast amounts of text. It can read natural language and infer meaning. An LLM reading a response that contains a link labeled \"add-to-cart\" understands what that link does, because it has seen that phrase and its usage patterns in its training data.\n\nThe LLM is the first client that can actually read and understand HATEOAS links. It does not need a programmer to hard-code the meaning of every link. It can discover the API's structure by reading the responses, the same way a human discovers a website by reading the links on each page.\n\nThis is what Fielding described in 2000. It just needed a reader that could do the reading.\n\n### How It Connects to Other Ideas\n\n- **Object Interface Protocol (OIP):** OIP defines how objects communicate across systems. REST's HATEOAS constraint, combined with an LLM as the client, means OIP endpoints can describe themselves. An LLM-driven agent can read an OIP endpoint's hypermedia response and understand what operations are available without prior documentation.\n- **Semantic Web:** Tim Berners-Lee's vision of machines traversing linked data graphs also failed for the same reason — no machine could *understand* what it was traversing. LLMs solve that problem too.\n- **Capability security:** Mark Miller's work on capability-based systems (possession conveys authority) aligns with REST's statelessness — each request carries its own credentials, just as each capability reference carries its own authority.\n\n### Sources\n\n- Fielding, Roy Thomas. \"Architectural Styles and the Design of Network-based Software Architectures.\" Ph.D. dissertation, University of California, Irvine, 2000. Chapter 5 covers REST.\n- Fielding's blog posts clarifying REST vs. HTTP APIs (2008), available via the Internet Archive.\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-roy-fielding`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-roy-fielding`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Roy%20Fielding%20%E2%80%94%20The%20Man%20Who%20Named%20How%20the%20Web%20Works`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-roy-fielding"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-roy-fielding/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:45.806Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"36d2ffbf9f434b0bc395bcaae4c492b97efd7b19e3d909f0f565cdefce591c48"},{"ts":"2026-07-17T02:42:58.697Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-roy-fielding","response":"32 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"36d2ffbf9f434b0bc395bcaae4c492b97efd7b19e3d909f0f565cdefce591c48","hash":"2facfb6f75004a11ad67a8d89b360b470f433c1139e92a2f474dd5711f1eb80a"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"2facfb6f75004a11ad67a8d89b360b470f433c1139e92a2f474dd5711f1eb80a"},"posted_at":"2026-07-15T04:20:45.806Z","created_at":"2026-07-15T04:20:45.806Z","updated_at":"2026-07-17T02:42:58.697Z","machine":{"shape":"article.machine/v1","slug":"thinker-roy-fielding","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-roy-fielding","json":"https://miscsubjects.com/api/articles/thinker-roy-fielding","bundle":"https://miscsubjects.com/api/articles/thinker-roy-fielding/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-roy-fielding/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-roy-fielding","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-roy-fielding\",\"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-roy-fielding\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-roy-fielding/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-roy-fielding\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-roy-fielding | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-roy-fielding","json":"/api/articles/thinker-roy-fielding","markdown":"/api/articles/thinker-roy-fielding/bundle?format=markdown","skill":"/api/articles/thinker-roy-fielding/skill","topology":"/api/articles/thinker-roy-fielding/topology","versions":"/api/articles/thinker-roy-fielding/revisions","invocations":"/api/articles/thinker-roy-fielding/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-roy-fielding","ok":false,"issues":[{"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":"c2d8b2da20e53d7ac4065a3117e3bdda7e18382ad7d04018621139cff6a426d2"}}}