{"_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":"what-is-hateoas","urls":{"read":"https://miscsubjects.com/api/articles/what-is-hateoas/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/what-is-hateoas/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/what-is-hateoas/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/what-is-hateoas/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/what-is-hateoas/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/what-is-hateoas/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/what-is-hateoas/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":"what-is-hateoas","title":"What Is HATEOAS","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-hateoas"],"updated_at":"2026-07-15T04:20:56.865Z","body_excerpt":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is HATEOAS**\n>\n> **Shelf:** Protocol Concepts · **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# What Is HATEOAS\n\n## §SELF — what-is-hateoas\n\n**What this page is:** A definition of HATEOAS and an explanation of why it failed for 20 years and why it works now.\n**What it explains:** The concept of hypermedia-driven application state and how the emergence of language models makes it practically usable for the first time.\n**Why read it:** To understand why a long-neglected REST constraint is now relevant, and how it enables systems where clients discover actions dynamically rather than being hardcoded to fixed API endpoints.\n\n### What HATEOAS Is\n\nHATEOAS stands for \"Hypermedia as the Engine of Application State.\" The term was coined by Roy Fielding in Chapter 5 of his 2000 doctoral dissertation, which defined the REST (Representational State Transfer) architectural style.\n\nThe core idea: every response from a server contains not only the requested data but also links that describe what actions are possible next. The client does not need prior knowledge of the API structure, endpoint URLs, or available operations. It reads the response, finds the links, and decides which to follow. The application's state is advanced entirely by the hypermedia (links) returned by the server — hence \"the engine of application state.\"\n\nExample: a client requests a user resource. The server responds with the user's data plus links: `\"edit\": \"/users/42/edit\"`, `\"delete\": \"/users/42\"`, `\"orders\": \"/users/42/orders\"`. The client reads these links and knows what it can do next. If the server removes the delete link, the client knows deletion is no longer an option. The client did not need to check a specification document. The response told it everything.\n\n### Why It Matters\n\nHATEOAS decouples the client from the server's API structure. The server can change URLs, add operations, or remove operations without breaking clients. Clients written to follow links adapt automatically. In a non-HATEOAS API, a URL change breaks every hardcoded client. In a HATEOAS API, the server changes its response, and clients follow the new links without modification.\n\nThis matters for long-lived systems where APIs evolve. It also matters for systems where clients need to navigate complex or variable workflows (multi-step processes, conditional paths, state-dependent options) without being programmed for every possible path in advance.\n\n### The Key Idea\n\nThe server's response is self-describing. It contains both data and controls. The client discovers actions at runtime, not at compile time.\n\nFielding's REST dissertation specified this as a constraint: a RESTful application must be driven by hypermedia. A server returning JSON data alone is not HATEOAS. A server returning JSON data plus links to related actions and resources is HATEOAS.\n\nThe client needs no API specification (no OpenAPI document, no Swagger file, no documentation). The response itself specifies the available state transitions. This is how the World Wide Web works for humans: a web page contains links. You read the page, see the links, and click one. You did not need a manual to know what links a page would contain.\n\n### What It Got Right\n\n- **Runtime discovery of API capabilities.** Clients adapt to API changes without code modification. This reduces coupling between client and server.\n- **Self-documenting responses.** Each response carries its own instructions for what can happen next. No external documentation is needed to navigate the API.\n- **State-appropriate controls.** The server can include or exclude links based o","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"what-is-hateoas","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}}