{"slug":"oip-glossary","title":"The OIP glossary","body":"## What the concept is\n\nOIP stands for Object Invocation Protocol.\nIt is a way to call code objects by sending a plain web address.\n\nAn object is a named piece of code stored on the server.\nA key is the name that points to one object.\n\nA capability is what one object can do when it runs.\nA token is a short string that proves you are allowed to run an object.\n\nA tenant is one user or team that owns objects inside the system.\n\nA dispatch is the act of sending a request that makes an object run.\nThe route POST /api/dispatch {key, body} starts a dispatch.\nThe route GET /api/dispatch?invoke=KEY&body=... also starts a dispatch.\n\nA receipt is the proof that a dispatch happened.\nEvery receipt lives at /api/dispatch?receipt=inv_ID.\nThe ledger is the permanent list of all receipts.\n\nREST stands for Representational State Transfer.\nIt is the style of web addresses used by OIP.\n\nCLI stands for Command Line Interface.\nIt is a text program you run in a terminal to talk to OIP.\n\nJSON stands for JavaScript Object Notation.\nIt is a simple text format for sending data.\n\nMCP stands for Model Context Protocol.\nMCP is an open standard that keeps an open session between a model and a server.\nThe MCP server gives the model tools, resources, and prompts.\nOIP has no session; any model that can open a URL can call objects.\n\n## Why this build cares about it\n\nEvery term above appears in other OIP articles.\nA single glossary stops repeated explanations.\nIt also makes the machine-native JSON easier to read.\n\n## How to see or use it live with curl against https://miscsubjects.com\n\nYou cannot fetch the glossary with one curl because it is a static page.\nYou can fetch the article at the route /a/oip-glossary.\nYou can test any term by running a dispatch.\nExample:\ncurl -X POST https://miscsubjects.com/api/dispatch \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"key\":\"oip-tap-go\",\"body\":{}}'\nThis uses the exact route POST /api/dispatch.\nThe response contains a receipt URL.\n\n## How it relates to MCP when relevant\n\nMCP keeps a live session and lists tools the model can call.\nOIP uses one-shot URLs and receipts instead.\nNo open connection is needed.\n\n## Where the proof lives\n\nEvery dispatch writes one row in the append-only ledger.\nThe receipt at /api/dispatch?receipt=inv_ID shows the exact key, body, and result.\nThese receipts are the only source of truth for the glossary terms.","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","dynamic"],"style":{"accent":"#16324f","measure":860},"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"prov":{"model":"system/oip_articles","action":"generate"}}