{"slug":"oip-from-rest","title":"What OIP Should Take from REST","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [OIP Lineages](https://miscsubjects.com/a/oip-from-lineages) › **What OIP Should Take from REST**\n>\n> **Shelf:** OIP Lineages · **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 OIP Should Take from REST\n\n## §SELF — oip-from-rest\n\n**What this page is:** A breakdown of which REST architectural principles OIP adopts, which it rejects, and what OIP adds that REST lacks.\n**What it explains:** REST's five core constraints and how OIP applies each one to model-to-model interaction.\n**Why read it:** To understand why OIP's design choices are not arbitrary — they extend a proven architectural style.\n\n### What REST Is\n\nREST (Representational State Transfer) is an architectural style for networked systems defined by Roy Fielding in his 2000 doctoral dissertation. A RESTful system organizes interaction around resources, each identified by a URL, manipulated through a small set of uniform operations, and represented in a standard format. The server does not store client state between requests.\n\n### Why It Matters\n\nREST became the dominant architecture for web APIs because it scales. Statelessness lets servers handle any request without knowing prior history. Uniform interfaces let clients interact with any resource the same way. Cacheability reduces load. These properties matter more, not less, when the clients are autonomous models rather than human-driven applications.\n\n### The Key Idea\n\nOIP treats every model-deployed object as a resource and every interaction as a stateless, cacheable, self-describing operation against that resource. OIP does not copy REST wholesale. OIP extends REST's constraints to fit a world where the clients are models, the operations are work objects, and the proof of execution is a first-class entity.\n\n### What OIP Takes from REST\n\n**The uniform interface.** REST says one endpoint handles all operations on all resources. OIP takes this to its limit: a single dispatch door (`/api/dispatch`) receives every invocation. The specific operation is determined by the capability token and object key carried in the request, not by the URL path. One door. All objects.\n\n**Statelessness.** Every request contains all information needed to process it. The server stores no client session, no connection context, no remembered state. OIP follows this: every invocation carries the full capability token and the full object key. The server does not need to know who sent the request or what they did before. The request is self-sufficient.\n\n**Resource identification.** Every resource in REST has a unique URL. OIP extends this: every object has a unique URL, every receipt has a unique URL, every capability token is bound to a unique object URL. The URL is not just an address. It is the permanent identity of the thing.\n\n**HATEOAS (Hypermedia as the Engine of Application State).** REST responses contain links to possible next actions, so a client can navigate the API without prior knowledge of its structure. OIP's §SELF blocks and capability records serve the same function for model consumption. A model receives a capability record and knows, from that record alone, what operations it can perform and where to send the next request. The response carries its own navigation instructions.\n\n**Cacheability.** REST responses carry metadata indicating whether they can be cached and for how long. OIP receipts are immutable — once created, they never change. An immutable receipt is infinitely cacheable. Any cache, anywhere, can store it forever without risk of stale data.\n\n### What OIP Does Not Take from REST\n\nREST's emphasis on CRUD (Create, Read, Update, Delete). CRUD assumes the resources are data records to be stored and modified. OIP's objects are not data resources. They are work objects — running processes, active capabilities, executable contracts. An OIP object performs work; it is not a row in a table. The CRUD mindset misleads because it treats everything as storage. OIP treats everything as execution.\n\n### What OIP Adds That REST Lacked\n\n**Capability tokens.** REST relies on external authentication (API keys, OAuth, session cookies) to decide who can do what. OIP embeds the authority in the token itself. The capability token is the permission. This is capability security, not identity security.\n\n**Receipts.** REST has no native concept of proof of execution. A REST response is a reply; an OIP receipt is a permanent, verifiable record that an operation occurred, signed by the executing object, stored at a URL, and referenceable forever.\n\n**Replay and repair.** REST operations are fire-and-forget. If a request fails, the client retries blindly. OIP's receipt lineage lets a caller trace an operation through every stage, detect where it diverged from expectation, and repair the specific failed step without re-executing the whole chain.\n\n**Model-readable contracts.** REST APIs require human-readable documentation (OpenAPI specs, etc.) that a model cannot interpret at runtime. OIP object contracts are structured so a model can read them, understand what operations are available, what parameters each requires, and what responses each produces — all without human intervention.\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 defines REST.)\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- [OIP Lineages shelf](https://miscsubjects.com/a/oip-from-lineages) — 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 OIP Should Take from Capability Security](https://miscsubjects.com/a/oip-from-capability-security)\n- [What OIP Should Take from the Semantic Web](https://miscsubjects.com/a/oip-from-semantic-web)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/oip-from-rest`\n- JSON article: `https://miscsubjects.com/api/articles/oip-from-rest`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20OIP%20Should%20Take%20from%20REST`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","lineages","oip-from-rest"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/oip-from-rest/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: OIP Lineages (oip-from-lineages). 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":3,"label":"OIP Lineages on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:24.145Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"5815887230b3bb3dc2a83f79d834afa5703d348b07036fa62bc4ad755ba2f076"},{"ts":"2026-07-17T02:36:12.886Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-from-rest","response":"33 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"5815887230b3bb3dc2a83f79d834afa5703d348b07036fa62bc4ad755ba2f076","hash":"93a03cdbdd80c72d974f10fd80663f8c7377fec926313a3a8d1d7ba406791ecb"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"93a03cdbdd80c72d974f10fd80663f8c7377fec926313a3a8d1d7ba406791ecb"},"posted_at":"2026-07-15T04:20:24.145Z","created_at":"2026-07-15T04:20:24.145Z","updated_at":"2026-07-17T02:36:12.886Z","machine":{"shape":"article.machine/v1","slug":"oip-from-rest","kind":"article","read":{"human":"https://miscsubjects.com/a/oip-from-rest","json":"https://miscsubjects.com/api/articles/oip-from-rest","bundle":"https://miscsubjects.com/api/articles/oip-from-rest/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/oip-from-rest/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-from-rest","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\":\"oip-from-rest\",\"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\":\"oip-from-rest\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-from-rest/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\":\"oip-from-rest\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-from-rest | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-from-rest","json":"/api/articles/oip-from-rest","markdown":"/api/articles/oip-from-rest/bundle?format=markdown","skill":"/api/articles/oip-from-rest/skill","topology":"/api/articles/oip-from-rest/topology","versions":"/api/articles/oip-from-rest/revisions","invocations":"/api/articles/oip-from-rest/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-from-rest","slug":"oip-from-rest","title":"What OIP Should Take from REST"},"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/oip-from-rest","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-from-rest/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-from-rest\ndescription: Apply the What OIP Should Take from REST article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What OIP Should Take from REST\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-from-rest). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-from-rest.\n- Read claims and relationships at /api/articles/oip-from-rest/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 › OIP Lineages https://miscsubjects.com/a/oip-from-lineages › What OIP Should Take from REST Shelf: OIP Line\n\n## Representations\n\n- Human: /a/oip-from-rest\n- JSON: /api/articles/oip-from-rest\n- Relationships: /api/articles/oip-from-rest/topology\n- History: /api/articles/oip-from-rest/revisions\n"},"json":{"route":"/api/articles/oip-from-rest","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-from-rest/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: Cyrus 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: Cyrus says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.cyrus.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/massoumicyrus/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: Cyrus 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: Cyrus 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/massoumicyrus/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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","lineages","oip-from-rest","oip","from","rest"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-from-rest/invocations?status=success","failure_events":"/api/articles/oip-from-rest/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":"oip-from-rest","title":"What OIP Should Take from REST","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [OIP Lineages](https://miscsubjects.com/a/oip-from-lineages) › **What OIP Should Take from REST**\n>\n> **Shelf:** OIP Lineages · **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 OIP Should Take from REST\n\n## §SELF — oip-from-rest\n\n**What this page is:** A breakdown of which REST architectural principles OIP adopts, which it rejects, and what OIP adds that REST lacks.\n**What it explains:** REST's five core constraints and how OIP applies each one to model-to-model interaction.\n**Why read it:** To understand why OIP's design choices are not arbitrary — they extend a proven architectural style.\n\n### What REST Is\n\nREST (Representational State Transfer) is an architectural style for networked systems defined by Roy Fielding in his 2000 doctoral dissertation. A RESTful system organizes interaction around resources, each identified by a URL, manipulated through a small set of uniform operations, and represented in a standard format. The server does not store client state between requests.\n\n### Why It Matters\n\nREST became the dominant architecture for web APIs because it scales. Statelessness lets servers handle any request without knowing prior history. Uniform interfaces let clients interact with any resource the same way. Cacheability reduces load. These properties matter more, not less, when the clients are autonomous models rather than human-driven applications.\n\n### The Key Idea\n\nOIP treats every model-deployed object as a resource and every interaction as a stateless, cacheable, self-describing operation against that resource. OIP does not copy REST wholesale. OIP extends REST's constraints to fit a world where the clients are models, the operations are work objects, and the proof of execution is a first-class entity.\n\n### What OIP Takes from REST\n\n**The uniform interface.** REST says one endpoint handles all operations on all resources. OIP takes this to its limit: a single dispatch door (`/api/dispatch`) receives every invocation. The specific operation is determined by the capability token and object key carried in the request, not by the URL path. One door. All objects.\n\n**Statelessness.** Every request contains all information needed to process it. The server stores no client session, no connection context, no remembered state. OIP follows this: every invocation carries the full capability token and the full object key. The server does not need to know who sent the request or what they did before. The request is self-sufficient.\n\n**Resource identification.** Every resource in REST has a unique URL. OIP extends this: every object has a unique URL, every receipt has a unique URL, every capability token is bound to a unique object URL. The URL is not just an address. It is the permanent identity of the thing.\n\n**HATEOAS (Hypermedia as the Engine of Application State).** REST responses contain links to possible next actions, so a client can navigate the API without prior knowledge of its structure. OIP's §SELF blocks and capability records serve the same function for model consumption. A model receives a capability record and knows, from that record alone, what operations it can perform and where to send the next request. The response carries its own navigation instructions.\n\n**Cacheability.** REST responses carry metadata indicating whether they can be cached and for how long. OIP receipts are immutable — once created, they never change. An immutable receipt is infinitely cacheable. Any cache, anywhere, can store it forever without risk of stale data.\n\n### What OIP Does Not Take from REST\n\nREST's emphasis on CRUD (Create, Read, Update, Delete). CRUD assumes the resources are data records to be stored and modified. OIP's objects are not data resources. They are work objects — running processes, active capabilities, executable contracts. An OIP object performs work; it is not a row in a table. The CRUD mindset misleads because it treats everything as storage. OIP treats everything as execution.\n\n### What OIP Adds That REST Lacked\n\n**Capability tokens.** REST relies on external authentication (API keys, OAuth, session cookies) to decide who can do what. OIP embeds the authority in the token itself. The capability token is the permission. This is capability security, not identity security.\n\n**Receipts.** REST has no native concept of proof of execution. A REST response is a reply; an OIP receipt is a permanent, verifiable record that an operation occurred, signed by the executing object, stored at a URL, and referenceable forever.\n\n**Replay and repair.** REST operations are fire-and-forget. If a request fails, the client retries blindly. OIP's receipt lineage lets a caller trace an operation through every stage, detect where it diverged from expectation, and repair the specific failed step without re-executing the whole chain.\n\n**Model-readable contracts.** REST APIs require human-readable documentation (OpenAPI specs, etc.) that a model cannot interpret at runtime. OIP object contracts are structured so a model can read them, understand what operations are available, what parameters each requires, and what responses each produces — all without human intervention.\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 defines REST.)\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- [OIP Lineages shelf](https://miscsubjects.com/a/oip-from-lineages) — 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 OIP Should Take from Capability Security](https://miscsubjects.com/a/oip-from-capability-security)\n- [What OIP Should Take from the Semantic Web](https://miscsubjects.com/a/oip-from-semantic-web)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/oip-from-rest`\n- JSON article: `https://miscsubjects.com/api/articles/oip-from-rest`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20OIP%20Should%20Take%20from%20REST`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","lineages","oip-from-rest"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/oip-from-rest/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: OIP Lineages (oip-from-lineages). 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":3,"label":"OIP Lineages on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:24.145Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"5815887230b3bb3dc2a83f79d834afa5703d348b07036fa62bc4ad755ba2f076"},{"ts":"2026-07-17T02:36:12.886Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-from-rest","response":"33 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"5815887230b3bb3dc2a83f79d834afa5703d348b07036fa62bc4ad755ba2f076","hash":"93a03cdbdd80c72d974f10fd80663f8c7377fec926313a3a8d1d7ba406791ecb"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"93a03cdbdd80c72d974f10fd80663f8c7377fec926313a3a8d1d7ba406791ecb"},"posted_at":"2026-07-15T04:20:24.145Z","created_at":"2026-07-15T04:20:24.145Z","updated_at":"2026-07-17T02:36:12.886Z","machine":{"shape":"article.machine/v1","slug":"oip-from-rest","kind":"article","read":{"human":"https://miscsubjects.com/a/oip-from-rest","json":"https://miscsubjects.com/api/articles/oip-from-rest","bundle":"https://miscsubjects.com/api/articles/oip-from-rest/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/oip-from-rest/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-from-rest","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\":\"oip-from-rest\",\"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\":\"oip-from-rest\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-from-rest/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\":\"oip-from-rest\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-from-rest | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-from-rest","json":"/api/articles/oip-from-rest","markdown":"/api/articles/oip-from-rest/bundle?format=markdown","skill":"/api/articles/oip-from-rest/skill","topology":"/api/articles/oip-from-rest/topology","versions":"/api/articles/oip-from-rest/revisions","invocations":"/api/articles/oip-from-rest/invocations"}}}}