{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"thinker-roy-fielding","urls":{"read":"https://miscsubjects.com/api/articles/thinker-roy-fielding/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/thinker-roy-fielding/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-roy-fielding/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-roy-fielding/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/thinker-roy-fielding/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-roy-fielding/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/thinker-roy-fielding/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"thinker-roy-fielding","title":"Roy Fielding — The Man Who Named How the Web Works","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-roy-fielding"],"updated_at":"2026-07-15T04:20:45.806Z","body_excerpt":"<!-- 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 wo","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"thinker-roy-fielding","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":0,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":0,"claims_total":0,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}