{"_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":"what-is-hateoas","title":"What Is HATEOAS","body":"<!-- 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 on the current state. A resource in a non-deletable state simply omits the delete link. The client does not need conditional logic to know what is allowed — the server tells it.\n\n### What It Got Wrong or Left Unfinished\n\n- **Traditional clients cannot read links and decide what to do.** Web browsers can do this for HTML — they render links for humans to click. But programmatic clients (scripts, mobile apps, backend services) are hardcoded to specific URLs and HTTP methods. They cannot parse a JSON response, discover links, and autonomously select an action. They need a human programmer to write that logic.\n- **No machine-readable semantics for links.** Even if a client finds a link labeled `\"edit\"`, it does not know what HTTP method to use, what parameters to send, or what the action does without a specification. HTML has semantic conventions (`<a>` for GET, `<form>` for POST with fields). JSON link formats (RFC 5988, JSON Hyper-Schema, HAL) attempted to add semantics but never achieved wide adoption.\n- **It failed for 20 years because the reader did not exist.** HATEOAS required a client that could read a response, understand the meaning of embedded links, and make decisions about which to follow. Traditional software cannot do this. A human reading HTML in a browser can, but programmatic APIs are designed for deterministic, pre-coded clients.\n\n### How It Connects to Other Ideas\n\n- **REST architecture:** HATEOAS is one of the architectural constraints that Fielding defined for REST, alongside statelessness, cacheability, and a uniform interface. Most APIs described as \"RESTful\" implement only the other constraints and omit HATEOAS.\n- **Language models (LLMs):** A language model can read a response, identify links, understand their semantic labels, and decide which link to follow based on a goal. This capability did not exist when HATEOAS was specified. It exists now. HATEOAS was a protocol waiting for a reader. The reader has arrived.\n\n### Sources\n\n- Fielding, Roy Thomas. \"Architectural Styles and the Design of Network-based Software Architectures.\" Doctoral dissertation, University of California, Irvine, 2000. Chapter 5: Representational State Transfer (REST).\n- RFC 5988: Web Linking (IETF, 2010).\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- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — 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- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Convergence Catalogue](https://miscsubjects.com/a/what-is-convergence-catalogue)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is the History of Link Protocols](https://miscsubjects.com/a/what-is-link-protocol-history)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-hateoas`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-hateoas`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20HATEOAS`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: affordances are computed for the credential; omitted moves are denied by the server, not by documentation prose.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-hateoas","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-hateoas/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: Protocol Concepts (oip-protocol-concepts). 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":20,"label":"Protocol Concepts on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: affordances are computed for the credential; omitted moves are denied by the server, not by documentation prose."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:56.865Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"d6a1cb67fbcbefb9eb208beade4ca5fbff0733a20999e57ed22249e849c48bba"},{"ts":"2026-07-15T06:24:50.924Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"d6a1cb67fbcbefb9eb208beade4ca5fbff0733a20999e57ed22249e849c48bba","hash":"3e9927a427743b14af9eb4aa452e50f018c34a025e014f12fa5d228df393182f"},{"ts":"2026-07-17T02:43:37.875Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-hateoas","response":"34 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"3e9927a427743b14af9eb4aa452e50f018c34a025e014f12fa5d228df393182f","hash":"ab565c9d146ca83c0900b3234c9bf6bc4de5238f84dfa74a3730da0b0e448679"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"ab565c9d146ca83c0900b3234c9bf6bc4de5238f84dfa74a3730da0b0e448679"},"posted_at":"2026-07-15T04:20:56.865Z","created_at":"2026-07-15T04:20:56.865Z","updated_at":"2026-07-17T02:43:37.875Z","machine":{"shape":"article.machine/v1","slug":"what-is-hateoas","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-hateoas","json":"https://miscsubjects.com/api/articles/what-is-hateoas","bundle":"https://miscsubjects.com/api/articles/what-is-hateoas/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-hateoas/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-hateoas","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\":\"what-is-hateoas\",\"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\":\"what-is-hateoas\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-hateoas/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\":\"what-is-hateoas\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-hateoas | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-hateoas","json":"/api/articles/what-is-hateoas","markdown":"/api/articles/what-is-hateoas/bundle?format=markdown","skill":"/api/articles/what-is-hateoas/skill","topology":"/api/articles/what-is-hateoas/topology","versions":"/api/articles/what-is-hateoas/revisions","invocations":"/api/articles/what-is-hateoas/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-hateoas","ok":false,"issues":[{"code":"headline_quality","message":"headline is too short to orient a cold reader; name the subject and event: \"What Is HATEOAS\"","replacement":"Write a shorter literal headline naming the article subject and its central event or claim."},{"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":"58feafc45a86c02da82d1b84f2b2b66a9e41b5d84bdceb4db204baf0b2f18ae7","object":{"object_type":"article-object","identity":{"id":"article:what-is-hateoas","slug":"what-is-hateoas","title":"What Is HATEOAS"},"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/what-is-hateoas","role":"explain","audience":"human"},"skill":{"route":"/api/articles/what-is-hateoas/skill","role":"direct behavior","audience":"model","content":"---\nname: what-is-hateoas\ndescription: Apply the What Is HATEOAS article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What Is HATEOAS\n\nThis Skill is the behavioral expression of [the canonical article](/a/what-is-hateoas). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/what-is-hateoas.\n- Read claims and relationships at /api/articles/what-is-hateoas/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 › Protocol Concepts https://miscsubjects.com/a/oip-protocol-concepts › What Is HATEOAS Shelf: Protocol Conce\n\n## Representations\n\n- Human: /a/what-is-hateoas\n- JSON: /api/articles/what-is-hateoas\n- Relationships: /api/articles/what-is-hateoas/topology\n- History: /api/articles/what-is-hateoas/revisions\n"},"json":{"route":"/api/articles/what-is-hateoas","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/what-is-hateoas/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","concepts","what-is-hateoas","objection-7","oip-edge","what","is","hateoas"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/what-is-hateoas/invocations?status=success","failure_events":"/api/articles/what-is-hateoas/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":"what-is-hateoas","title":"What Is HATEOAS","body":"<!-- 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 on the current state. A resource in a non-deletable state simply omits the delete link. The client does not need conditional logic to know what is allowed — the server tells it.\n\n### What It Got Wrong or Left Unfinished\n\n- **Traditional clients cannot read links and decide what to do.** Web browsers can do this for HTML — they render links for humans to click. But programmatic clients (scripts, mobile apps, backend services) are hardcoded to specific URLs and HTTP methods. They cannot parse a JSON response, discover links, and autonomously select an action. They need a human programmer to write that logic.\n- **No machine-readable semantics for links.** Even if a client finds a link labeled `\"edit\"`, it does not know what HTTP method to use, what parameters to send, or what the action does without a specification. HTML has semantic conventions (`<a>` for GET, `<form>` for POST with fields). JSON link formats (RFC 5988, JSON Hyper-Schema, HAL) attempted to add semantics but never achieved wide adoption.\n- **It failed for 20 years because the reader did not exist.** HATEOAS required a client that could read a response, understand the meaning of embedded links, and make decisions about which to follow. Traditional software cannot do this. A human reading HTML in a browser can, but programmatic APIs are designed for deterministic, pre-coded clients.\n\n### How It Connects to Other Ideas\n\n- **REST architecture:** HATEOAS is one of the architectural constraints that Fielding defined for REST, alongside statelessness, cacheability, and a uniform interface. Most APIs described as \"RESTful\" implement only the other constraints and omit HATEOAS.\n- **Language models (LLMs):** A language model can read a response, identify links, understand their semantic labels, and decide which link to follow based on a goal. This capability did not exist when HATEOAS was specified. It exists now. HATEOAS was a protocol waiting for a reader. The reader has arrived.\n\n### Sources\n\n- Fielding, Roy Thomas. \"Architectural Styles and the Design of Network-based Software Architectures.\" Doctoral dissertation, University of California, Irvine, 2000. Chapter 5: Representational State Transfer (REST).\n- RFC 5988: Web Linking (IETF, 2010).\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- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — 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- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Convergence Catalogue](https://miscsubjects.com/a/what-is-convergence-catalogue)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is the History of Link Protocols](https://miscsubjects.com/a/what-is-link-protocol-history)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-hateoas`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-hateoas`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20HATEOAS`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: affordances are computed for the credential; omitted moves are denied by the server, not by documentation prose.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-hateoas","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-hateoas/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: Protocol Concepts (oip-protocol-concepts). 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":20,"label":"Protocol Concepts on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: affordances are computed for the credential; omitted moves are denied by the server, not by documentation prose."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:56.865Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"d6a1cb67fbcbefb9eb208beade4ca5fbff0733a20999e57ed22249e849c48bba"},{"ts":"2026-07-15T06:24:50.924Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"d6a1cb67fbcbefb9eb208beade4ca5fbff0733a20999e57ed22249e849c48bba","hash":"3e9927a427743b14af9eb4aa452e50f018c34a025e014f12fa5d228df393182f"},{"ts":"2026-07-17T02:43:37.875Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-hateoas","response":"34 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"3e9927a427743b14af9eb4aa452e50f018c34a025e014f12fa5d228df393182f","hash":"ab565c9d146ca83c0900b3234c9bf6bc4de5238f84dfa74a3730da0b0e448679"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"ab565c9d146ca83c0900b3234c9bf6bc4de5238f84dfa74a3730da0b0e448679"},"posted_at":"2026-07-15T04:20:56.865Z","created_at":"2026-07-15T04:20:56.865Z","updated_at":"2026-07-17T02:43:37.875Z","machine":{"shape":"article.machine/v1","slug":"what-is-hateoas","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-hateoas","json":"https://miscsubjects.com/api/articles/what-is-hateoas","bundle":"https://miscsubjects.com/api/articles/what-is-hateoas/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-hateoas/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-hateoas","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\":\"what-is-hateoas\",\"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\":\"what-is-hateoas\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-hateoas/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\":\"what-is-hateoas\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-hateoas | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-hateoas","json":"/api/articles/what-is-hateoas","markdown":"/api/articles/what-is-hateoas/bundle?format=markdown","skill":"/api/articles/what-is-hateoas/skill","topology":"/api/articles/what-is-hateoas/topology","versions":"/api/articles/what-is-hateoas/revisions","invocations":"/api/articles/what-is-hateoas/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-hateoas","ok":false,"issues":[{"code":"headline_quality","message":"headline is too short to orient a cold reader; name the subject and event: \"What Is HATEOAS\"","replacement":"Write a shorter literal headline naming the article subject and its central event or claim."},{"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":"58feafc45a86c02da82d1b84f2b2b66a9e41b5d84bdceb4db204baf0b2f18ae7"}}}