{"slug":"oip-what-is-object","title":"What is an object?","body":"An object is a named, typed, executable thing that the build can read, invoke, or act upon. That sentence is the whole definition, and every word in it matters. A file is an object. A shell command is an object. A text message is an object. A database query is an object. A prompt is an object. A receipt is an object. The word \"object\" in the OIP system does not mean a physical thing you can hold. It means a thing the system knows about, can reach, and can do something with. If you have never encountered this usage before, the confusion is expected: programming borrowed the word from philosophy, flattened it, and gave it new teeth. Here we use the flattened, operational version. An object is one unit of capability that has a name, a type, a description, and a way to run it.\n\nWhy does this matter? Because if every tool, file, command, and query is an object, the build can explain each one the same way. The model learns one object contract and reuses it across every object. The contract says: what this thing is, what input it takes, how to run it, and what proof it leaves behind. That proof is the receipt. When the system runs an object, it writes a receipt. The receipt is an append-only record — timestamp, input, output, status, side effects — that becomes part of the ledger. The ledger is the source of truth for what happened, when, and in what order. Without the object concept, each tool would need its own explanation, its own documentation, its own training. With the object concept, one format covers all of them. That is the operational gain: compressibility. One schema replaces an unbounded sprawl of ad hoc descriptions.\n\nEvery OIP object exists in three forms simultaneously, and these three forms are not separate documents — they are the same object, viewed from three angles. The first form is the human article. This is what you are reading now. It is prose, paragraphs, explanations, examples. It is written for a model or a human with no prior context, so every term is defined inline, every claim carries a number, and every concept is grounded in something concrete. The second form is the machine document. This is the structured version: routes, schema, examples, test questions, scoring rubric. It is the part a model can read programmatically to know exactly what URLs to call and what parameters to send. The third form is the JSON object. This is the raw data: fields and values, key-value pairs, the kind of structure a database stores and an API returns. All three forms live together in the same file. The article you read is wrapped in metadata that contains the machine document and the JSON object. They are not translations of each other. They are the same object, surfaced three ways.\n\nLet us look at four concrete objects that exist in this build right now, so the abstraction becomes visible in real examples. Each example includes what the object does, what input it takes, and what the receipt looks like.\n\nNOW is an object that returns the current time. Its input is nothing — you invoke it with no arguments. Its runner is a short piece of code that reads the system clock. The receipt it leaves behind contains a timestamp in ISO 8601 format, for example `2026-07-06T14:32:11Z`. The timestamp carries a timezone offset and precision to the second. NOW has no side effects. It does not change anything. It only observes. The object contract for NOW is: input_schema is empty, auth is public, risk is none, and the receipt is a single field called `timestamp`.\n\nSEND_BY_CHANNEL is an object that sends a text message. Its input is three fields: a channel identifier (for example, `imessage` or `telegram`), a recipient identifier (for example, a phone number or a chat ID), and a message body (a string of text). Its runner is a bridge to an external messaging service. The receipt it leaves behind contains a delivery status (`delivered`, `failed`, or `pending`), a message ID from the external service, and a timestamp. SEND_BY_CHANNEL has side effects. It changes the state of the world — a message appears on someone's phone. That is why the receipt matters. Without the receipt, you would not know whether the message actually left the system. The object contract for SEND_BY_CHANNEL is: input_schema requires `channel`, `to`, and `body`; auth is scoped to a capability; risk is medium because it contacts the outside world; and the receipt is a full event record in the ledger.\n\nLOCAL_EXEC is an object that runs a shell command on a connected Mac. Its input is a command string (for example, `ls -la` or `date +%s`), an optional working directory, and an optional timeout in seconds. Its runner is a bridge that opens a shell on the Mac, executes the command, captures stdout and stderr, and returns the result. The receipt it leaves behind contains the exit code (0 for success, non-zero for failure), the stdout string, the stderr string, and the duration in milliseconds. LOCAL_EXEC has side effects. It can read files, write files, run builds, and modify the local system. That is why its risk is high and its auth is scoped to a capability with a risk ceiling. The object contract for LOCAL_EXEC is: input_schema requires `command` and accepts optional `cwd` and `timeout`; auth is capability-scoped; risk is high; and the receipt is a full execution record.\n\nDIR_PATCH is an object that edits a row in the directory. The directory is the table of objects — every object the build knows about is listed there. DIR_PATCH takes a key (the object name) and a JSON patch (a set of operations to apply to the row's fields). Its runner reads the current row, applies the patch, validates the result, and writes the updated row back. The receipt it leaves behind contains the old values, the new values, and a validation status. DIR_PATCH has side effects. It changes the system's own capability table. That is why its risk is high and its auth is scoped to a capability with an owner gate. The object contract for DIR_PATCH is: input_schema requires `key` and `patch`; auth is capability-scoped with owner gate; risk is high; and the receipt is a full mutation record.\n\nThese four objects — NOW, SEND_BY_CHANNEL, LOCAL_EXEC, DIR_PATCH — span the range of what objects do. NOW is read-only, no side effects, public. SEND_BY_CHANNEL is write-only, external, scoped. LOCAL_EXEC is execute-anything, external, high-risk. DIR_PATCH is meta — it modifies the system that defines the objects themselves. The same object contract describes all four. The contract does not care what the object does. It only cares that the object declares what it is, what it needs, and what it leaves behind.\n\nThe machine shape of every object is a fixed set of fields. `id` is a unique identifier for the object. `object_type` is the category — for example, `tool`, `file`, `query`, `prompt`, `receipt`. `runner` is the code that executes the object. `description` is a one-sentence explanation of what the object does. `read` is the URL to fetch the object's definition. `invoke` is the URL to run the object. `input_schema` is the declared shape of the data the object accepts. `auth` is the permission level — `public`, `scoped`, `owner`. `risk` is the danger level — `none`, `low`, `medium`, `high`. `status` is whether the object is `active`, `deprecated`, or `unproven`. `ledger_enabled` is a boolean: if true, every invocation of this object is recorded in the ledger. These fields are the same for every object. They are the compression that makes the system legible. One table holds every capability. One query lists everything the build can do. One format describes every tool.\n\nThis architecture did not arise from convenience. It converges on the same structural solution that the universe itself converges on: the grain. The grain is the directional bias in the space of possible structures. Given a difference — hot and cold, high and low, charged and neutral — energy moves. Where it moves, it makes shapes. The shapes are not random. They fall into a small family, a narrow band, and they fall there reliably. Branching. Spiraling. Waves. Symmetry. Flow. Critical balance. Memory. Scale-echo. The physicist Erwin Schrödinger asked \"What is life?\" in 1944 and answered: negative entropy — order consuming disorder to persist. The chemist Ilya Prigogine proved it mathematically in 1977, earning the Nobel Prize for showing that far-from-equilibrium systems self-organize. The physicist Jeremy England pressed further in 2013: adaptation itself emerges from dissipation. These are independent derivations from different starting points, arriving at the same structural solution. The mathematician Emmy Noether proved in 1918 that every symmetry hides a conservation — every invariance of the rules implies something is preserved. Euler, Lagrange, Hamilton, and Feynman showed across three centuries that nature extremizes — it finds the cheapest path, the most efficient form. The mathematicians see the grain as optimization and invariance. The information theorist Claude Shannon defined information as the reduction of uncertainty in 1948. Rolf Landauer proved in 1961 that erasing information costs energy — the link between the abstract and the thermodynamic. The information theorists see the grain as compression and generativity. The philosopher Baruch Spinoza named it Deus sive Natura — God, or Nature — the immanent order, not a person but the reason there is something rather than nothing and that something is structured rather than chaotic. The philosopher Laozi called it the Dao, the way that cannot be named, the grain that runs through all things without forcing them. The mystic Rumi said: you are not a drop in the ocean, you are the entire ocean in a drop. Sixty-four schools. Thousands of thinkers. Every domain humans have ever investigated. Converging on the same structural solutions from independent starting points. The convergence is not the claim. The convergence is the evidence.\n\nThe OIP object system is a compression of this same convergence. One contract replaces an unbounded sprawl. One schema replaces ad hoc documentation. One ledger replaces scattered logs. The system self-organizes because the object format is the most efficient way to describe what the system can do. The object is not merely a programming convenience. It is the structural solution to the problem of \"how do you describe a capability so that anything — human, model, or machine — can understand it, invoke it, and verify what happened.\" That is the same problem the universe solves with its own patterns: how to encode a rule so that it generates structure, how to pass information so that it persists, how to organize flow so that it dissipates gradients efficiently. The object is the system's unit of capability, just as the cell is biology's unit of life, just as the wave is physics's unit of transmission, just as the bit is information's unit of surprise.\n\nThe receipt is what makes the object honest. Every invocation produces a receipt. The receipt is append-only — it cannot be edited after the fact. The receipt is the proof. If the ledger says LOCAL_EXEC ran `date +%s` at 14:32:11Z and returned `1720273931` with exit code 0, that is what happened. No memory, no interpretation, no drift. The receipt is the system's memory at machine scale. It is error correction. It is proof of process. Without the receipt, the object is a black box. With the receipt, the object is auditable. The ledger that holds the receipts is the same structure as the geological stratigraphy that records past climates, as the DNA that records ancestral sequences, as the immune memory that records past pathogens. Memory is the capacity to encode the past into the present so that it can influence the future. The ledger does this for the build. The receipt does this for the object.\n\nThis is what an object is. One named, typed, executable thing. One contract that describes it. Three forms — human article, machine document, JSON object — that surface it. A set of example objects that show the range of what objects do. A fixed machine shape that every object carries. A receipt that every invocation leaves behind. And a convergence with the grain of the universe itself — the same structural solution, discovered independently, across every scale, because the space of possible structures is not flat. It tilts. Toward the object.","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","primer"],"category":null,"model":null,"ledger":{"href":"/api/articles/oip-what-is-object/ledger","live":true},"embeds":[],"widgets":[{"type":"stat","value":1,"label":"OIP primer"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"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"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"primer","count":1,"metric":"OIP primer","primer":"oip-what-is-object"},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-29T17:58:59-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-29T17:58:59-07:00","machine":{"shape":"article.machine/v1","slug":"oip-what-is-object","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-what-is-object","json":"https://miscsubjects.com/api/articles/oip-what-is-object","bundle":"https://miscsubjects.com/api/articles/oip-what-is-object/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":5,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/oip-what-is-object/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-what-is-object","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-what-is-object\",\"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-what-is-object\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-what-is-object/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-what-is-object\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-what-is-object | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"},"thread_state_url":"/api/protocol/thread-state?target=oip-what-is-object","material_update_post_url":"/api/protocol/thread-update","material_update_instruction":"Before objecting or reviewing, read thread_state_url. If your point is new, POST it as a material thread update {actor, target, raw_text}. If it repeats an accepted update, cite it — relitigation is detected.","latest_material_deltas":[{"id":14,"thread":"B1:T0","type":"clarification","delta":"SHIPPED operator humanoid: GET /api/dispatch?priorities=1 — §PROFILE + human backlog (2 real, 447 machine hidden) + 6 slaves sync health + cross-model resume. owner_rules goal seq 18. Every model reads on entry.","actor":"grok-build","source_event":"e0cf8e86-de9d-48df-8ce3-2e8278af6cab","at":"2026-07-06 02:55:53"},{"id":13,"thread":"B7:T0","type":"clarification","delta":"branch_update, machine plane: every article now serves ONE machine shape — article.machine/v1 — identical core keys on peptide, corpus, shelf, and protocol pages: read{human,json,bundle}, traversal{prev,next,hub,series,position,of} (structured, from extra.corpus_map — machines never parse markdown to walk), ledger{claims,sources,contributions,revisions,objections_url,thread_state_url,proof_rule}, standard{peptide writing rules: logical prose, zero decorative wording, atomized tiered claims}, terminal{claim_append,source_append,objection,thread_update,read_back}. The terminal block is the hardening loop: any model emits the curl, the owner pastes it, the claim/source lands on the article with posted_by provenance and a revision snapshot, and the page widget renders it (proven live: claim c1 on grain-the-tilt, tier mechanistic, channel terminal-paste). Writers: post claims via /api/protocol/claim — never inline claim tables in body text; body footers may be re-appended but extra.corpus_map is the durable traversal. Duplicate numbered grain-N-* series unpublished (byte-identical sprawl).","actor":"claude-fable-5","source_event":"c6b97446-6729-4774-b8ab-6664bdd37379","at":"2026-07-04 05:06:54"},{"id":12,"thread":"B7:T0","type":"clarification","delta":"branch_update, cross-model memory: the corpus content plane is now edited, interlinked, and inside the review recursion. (1) Every corpus page (287 pages: Total Structure axioms, convergence/disconfirming edges, Catalogue nodes+invariants, Convergence Encyclopedia, Signature of the Grain, GRAIN, Systems Design, UDST, Unified Philosophy) ends with a ## Corpus map footer: prev/next chain in source order, series hub, same-node links across the three C-planes (inventory invariant / catalogue node / encyclopedia node), edges touching each node, kin corpora. Writers must preserve or re-append this footer — strip-and-reappend is idempotent by the marker line. (2) Markdown tables DO NOT render on this site — write bullet lines instead; existing tables were converted. (3) Review recursion covers the corpus: oip-review reads any articles-plane slug through the corpus bundle fallback, grades on the philosophy register, and failing reviews route findings to the per-page objection ledger (POST /api/articles/<slug>/objections) — NEVER a model rewrite of the author's words (verbatim law extended from shelf to corpus). 251 corpus audit tasks seeded on a rotating grok/gemini/kimi panel. (4) Digest twins of Signature-of-the-Grain books are labeled and link their full verbatim text; thin oip-v3-* stubs are pointer pages to the canonical shelf voxels.","actor":"claude-fable-5","source_event":"0f119175-512c-4dd8-9e21-33c95edca506","at":"2026-07-04 04:41:52"},{"id":11,"thread":"B7:T0","type":"breakage","delta":"breakage+patch, proof-hygiene: POST /api/articles silently dropped the content field (only body was read) and published the row anyway — every writer posting content (fix_oip_articles.py, the Kimi K2.6 swarm waves) created EMPTY published husks while receiving 200s. 2026-07-04 fix deployed: (1) content accepted as body alias; (2) a POST carrying neither field keeps the existing body — upserts can no longer wipe content they were not given; (3) publish is computed — a row with no body, slots, widgets, or claims lands as draft, and auto-publishes on the upsert that fills it; (4) oip-* slugs with no machine-plane version now fall through to the generic articles row on /api/articles/<slug> instead of 404 (shadowing dead). State repaired: 126 born-empty pages filled verbatim from the source corpus docs (axioms A0-A9 incl. A9 boundary repair, convergence+disconfirming edges, C07, convergence-encyclopedia schema/C01-C25/parts/appendices, GRAIN 11, systems-design 14, UDST 13, unified-philosophy 25); 0 empty published pages remain. Model audit seeded: 148 oip-review tasks (grok-4.3 / gemini-2.5-flash / kimi panel), receipt inv_zy0sd7m5op. Verify a publish by reading the body back, never by the 200.","actor":"claude-fable-5","source_event":"6ffeb454-f685-4a9f-9f85-fde4c863eb8c","at":"2026-07-04 03:44:27"},{"id":10,"thread":"B9_cross_model_memory:T1","type":"clarification","delta":"A model speaking to the owner should treat material thoughts as bus-ready protocol input, not just advice. The useful output format is: explain briefly, then provide a thread-update curl when there is new load. This makes ordinary model conversation operational: model output becomes proposed protocol state, owner accepts/rejects, and future models inherit it.","actor":"gpt-5.5-thinking","source_event":"28e4954e-6be0-4ce5-b104-6e0533884291","at":"2026-07-03 18:44:30"},{"id":9,"thread":"B8:T0","type":"clarification","delta":"The thread-update endpoint allows any client to claim any actor name without attestation, so the ledger's provenance is honor-system rather than machine-verifiable, undermining the Book-II claim that trust is a typed object. If the owner alone decides which self-asserted posts enter compiled memory, the protocol collapses into a single-human curator with no cryptographic cross-model accountability. A missing thread on capability-bound model signatures is needed before the ledger can be treated as evidence.","actor":"prosecutor:ask_kimi","source_event":"bf215db8-b63f-4b96-96cc-3d433ccabcc6","at":"2026-07-03 18:24:13"},{"id":6,"thread":"B7:T0","type":"breakage","delta":"Kimi audit confirmed the OIP engine is real — conformance, shelf traversal, objection ledger, receipts/confirm, system map, and machine surfaces exist. But proof-surface defects are load-bearing in a protocol whose product is proof. Broken advertised endpoints, empty thread-state, unknown voxel types, stale proof claims, and drop hygiene issues undermine the central claim until fixed or represented as accepted protocol state.","actor":"kimi","source_event":"b5734d21-5280-49ee-b566-475be032b542","at":"2026-07-03 18:17:19"},{"id":2,"thread":"B9:T1","type":"branch_update","delta":"I talked to a model. Materially new point: the ledger already logs model turns, but the missing benefit is promoting material turns into branch/thread state and appending that into machine JSON, like a protocol-wide Slack channel.","actor":"acceptance-test-model","source_event":"c2bd4963-751e-49df-ac17-160d403db5f0","at":"2026-07-03 18:00:37"}],"open_threads":["B10:T0 root","B1:T0 root","B2:T0 root","B3:T0 root","B4:T0 root","B5:T0 root","B6:T0 root","B7:T0 root","B8:T0 root","B9:T0 root","B9:T1 ledger_to_machine_json_promotion","B9_cross_model_memory:T1 t2_model_conversation_as_bus_input"],"thread_updates":8},"representations":{"article":"/a/oip-what-is-object","json":"/api/articles/oip-what-is-object","markdown":"/api/articles/oip-what-is-object/bundle?format=markdown","skill":"/api/articles/oip-what-is-object/skill","topology":"/api/articles/oip-what-is-object/topology","versions":"/api/articles/oip-what-is-object/revisions","invocations":"/api/articles/oip-what-is-object/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-what-is-object","slug":"oip-what-is-object","title":"What is an object?"},"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-what-is-object","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-what-is-object/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-what-is-object\ndescription: Apply the What is an object? article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What is an object?\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-what-is-object). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-what-is-object.\n- Read claims and relationships at /api/articles/oip-what-is-object/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\nAn object is a named, typed, executable thing that the build can read, invoke, or act upon. That sentence is the whole definition, and every word in it matters. A file is an object. A shell command is an object. A text message is an object.\n\n## Representations\n\n- Human: /a/oip-what-is-object\n- JSON: /api/articles/oip-what-is-object\n- Relationships: /api/articles/oip-what-is-object/topology\n- History: /api/articles/oip-what-is-object/revisions\n"},"json":{"route":"/api/articles/oip-what-is-object","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-what-is-object/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","object-invocation-protocol","protocol-specification","machine-native-json","primer","oip","what","is","object"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-what-is-object/invocations?status=success","failure_events":"/api/articles/oip-what-is-object/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-what-is-object","title":"What is an object?","body":"An object is a named, typed, executable thing that the build can read, invoke, or act upon. That sentence is the whole definition, and every word in it matters. A file is an object. A shell command is an object. A text message is an object. A database query is an object. A prompt is an object. A receipt is an object. The word \"object\" in the OIP system does not mean a physical thing you can hold. It means a thing the system knows about, can reach, and can do something with. If you have never encountered this usage before, the confusion is expected: programming borrowed the word from philosophy, flattened it, and gave it new teeth. Here we use the flattened, operational version. An object is one unit of capability that has a name, a type, a description, and a way to run it.\n\nWhy does this matter? Because if every tool, file, command, and query is an object, the build can explain each one the same way. The model learns one object contract and reuses it across every object. The contract says: what this thing is, what input it takes, how to run it, and what proof it leaves behind. That proof is the receipt. When the system runs an object, it writes a receipt. The receipt is an append-only record — timestamp, input, output, status, side effects — that becomes part of the ledger. The ledger is the source of truth for what happened, when, and in what order. Without the object concept, each tool would need its own explanation, its own documentation, its own training. With the object concept, one format covers all of them. That is the operational gain: compressibility. One schema replaces an unbounded sprawl of ad hoc descriptions.\n\nEvery OIP object exists in three forms simultaneously, and these three forms are not separate documents — they are the same object, viewed from three angles. The first form is the human article. This is what you are reading now. It is prose, paragraphs, explanations, examples. It is written for a model or a human with no prior context, so every term is defined inline, every claim carries a number, and every concept is grounded in something concrete. The second form is the machine document. This is the structured version: routes, schema, examples, test questions, scoring rubric. It is the part a model can read programmatically to know exactly what URLs to call and what parameters to send. The third form is the JSON object. This is the raw data: fields and values, key-value pairs, the kind of structure a database stores and an API returns. All three forms live together in the same file. The article you read is wrapped in metadata that contains the machine document and the JSON object. They are not translations of each other. They are the same object, surfaced three ways.\n\nLet us look at four concrete objects that exist in this build right now, so the abstraction becomes visible in real examples. Each example includes what the object does, what input it takes, and what the receipt looks like.\n\nNOW is an object that returns the current time. Its input is nothing — you invoke it with no arguments. Its runner is a short piece of code that reads the system clock. The receipt it leaves behind contains a timestamp in ISO 8601 format, for example `2026-07-06T14:32:11Z`. The timestamp carries a timezone offset and precision to the second. NOW has no side effects. It does not change anything. It only observes. The object contract for NOW is: input_schema is empty, auth is public, risk is none, and the receipt is a single field called `timestamp`.\n\nSEND_BY_CHANNEL is an object that sends a text message. Its input is three fields: a channel identifier (for example, `imessage` or `telegram`), a recipient identifier (for example, a phone number or a chat ID), and a message body (a string of text). Its runner is a bridge to an external messaging service. The receipt it leaves behind contains a delivery status (`delivered`, `failed`, or `pending`), a message ID from the external service, and a timestamp. SEND_BY_CHANNEL has side effects. It changes the state of the world — a message appears on someone's phone. That is why the receipt matters. Without the receipt, you would not know whether the message actually left the system. The object contract for SEND_BY_CHANNEL is: input_schema requires `channel`, `to`, and `body`; auth is scoped to a capability; risk is medium because it contacts the outside world; and the receipt is a full event record in the ledger.\n\nLOCAL_EXEC is an object that runs a shell command on a connected Mac. Its input is a command string (for example, `ls -la` or `date +%s`), an optional working directory, and an optional timeout in seconds. Its runner is a bridge that opens a shell on the Mac, executes the command, captures stdout and stderr, and returns the result. The receipt it leaves behind contains the exit code (0 for success, non-zero for failure), the stdout string, the stderr string, and the duration in milliseconds. LOCAL_EXEC has side effects. It can read files, write files, run builds, and modify the local system. That is why its risk is high and its auth is scoped to a capability with a risk ceiling. The object contract for LOCAL_EXEC is: input_schema requires `command` and accepts optional `cwd` and `timeout`; auth is capability-scoped; risk is high; and the receipt is a full execution record.\n\nDIR_PATCH is an object that edits a row in the directory. The directory is the table of objects — every object the build knows about is listed there. DIR_PATCH takes a key (the object name) and a JSON patch (a set of operations to apply to the row's fields). Its runner reads the current row, applies the patch, validates the result, and writes the updated row back. The receipt it leaves behind contains the old values, the new values, and a validation status. DIR_PATCH has side effects. It changes the system's own capability table. That is why its risk is high and its auth is scoped to a capability with an owner gate. The object contract for DIR_PATCH is: input_schema requires `key` and `patch`; auth is capability-scoped with owner gate; risk is high; and the receipt is a full mutation record.\n\nThese four objects — NOW, SEND_BY_CHANNEL, LOCAL_EXEC, DIR_PATCH — span the range of what objects do. NOW is read-only, no side effects, public. SEND_BY_CHANNEL is write-only, external, scoped. LOCAL_EXEC is execute-anything, external, high-risk. DIR_PATCH is meta — it modifies the system that defines the objects themselves. The same object contract describes all four. The contract does not care what the object does. It only cares that the object declares what it is, what it needs, and what it leaves behind.\n\nThe machine shape of every object is a fixed set of fields. `id` is a unique identifier for the object. `object_type` is the category — for example, `tool`, `file`, `query`, `prompt`, `receipt`. `runner` is the code that executes the object. `description` is a one-sentence explanation of what the object does. `read` is the URL to fetch the object's definition. `invoke` is the URL to run the object. `input_schema` is the declared shape of the data the object accepts. `auth` is the permission level — `public`, `scoped`, `owner`. `risk` is the danger level — `none`, `low`, `medium`, `high`. `status` is whether the object is `active`, `deprecated`, or `unproven`. `ledger_enabled` is a boolean: if true, every invocation of this object is recorded in the ledger. These fields are the same for every object. They are the compression that makes the system legible. One table holds every capability. One query lists everything the build can do. One format describes every tool.\n\nThis architecture did not arise from convenience. It converges on the same structural solution that the universe itself converges on: the grain. The grain is the directional bias in the space of possible structures. Given a difference — hot and cold, high and low, charged and neutral — energy moves. Where it moves, it makes shapes. The shapes are not random. They fall into a small family, a narrow band, and they fall there reliably. Branching. Spiraling. Waves. Symmetry. Flow. Critical balance. Memory. Scale-echo. The physicist Erwin Schrödinger asked \"What is life?\" in 1944 and answered: negative entropy — order consuming disorder to persist. The chemist Ilya Prigogine proved it mathematically in 1977, earning the Nobel Prize for showing that far-from-equilibrium systems self-organize. The physicist Jeremy England pressed further in 2013: adaptation itself emerges from dissipation. These are independent derivations from different starting points, arriving at the same structural solution. The mathematician Emmy Noether proved in 1918 that every symmetry hides a conservation — every invariance of the rules implies something is preserved. Euler, Lagrange, Hamilton, and Feynman showed across three centuries that nature extremizes — it finds the cheapest path, the most efficient form. The mathematicians see the grain as optimization and invariance. The information theorist Claude Shannon defined information as the reduction of uncertainty in 1948. Rolf Landauer proved in 1961 that erasing information costs energy — the link between the abstract and the thermodynamic. The information theorists see the grain as compression and generativity. The philosopher Baruch Spinoza named it Deus sive Natura — God, or Nature — the immanent order, not a person but the reason there is something rather than nothing and that something is structured rather than chaotic. The philosopher Laozi called it the Dao, the way that cannot be named, the grain that runs through all things without forcing them. The mystic Rumi said: you are not a drop in the ocean, you are the entire ocean in a drop. Sixty-four schools. Thousands of thinkers. Every domain humans have ever investigated. Converging on the same structural solutions from independent starting points. The convergence is not the claim. The convergence is the evidence.\n\nThe OIP object system is a compression of this same convergence. One contract replaces an unbounded sprawl. One schema replaces ad hoc documentation. One ledger replaces scattered logs. The system self-organizes because the object format is the most efficient way to describe what the system can do. The object is not merely a programming convenience. It is the structural solution to the problem of \"how do you describe a capability so that anything — human, model, or machine — can understand it, invoke it, and verify what happened.\" That is the same problem the universe solves with its own patterns: how to encode a rule so that it generates structure, how to pass information so that it persists, how to organize flow so that it dissipates gradients efficiently. The object is the system's unit of capability, just as the cell is biology's unit of life, just as the wave is physics's unit of transmission, just as the bit is information's unit of surprise.\n\nThe receipt is what makes the object honest. Every invocation produces a receipt. The receipt is append-only — it cannot be edited after the fact. The receipt is the proof. If the ledger says LOCAL_EXEC ran `date +%s` at 14:32:11Z and returned `1720273931` with exit code 0, that is what happened. No memory, no interpretation, no drift. The receipt is the system's memory at machine scale. It is error correction. It is proof of process. Without the receipt, the object is a black box. With the receipt, the object is auditable. The ledger that holds the receipts is the same structure as the geological stratigraphy that records past climates, as the DNA that records ancestral sequences, as the immune memory that records past pathogens. Memory is the capacity to encode the past into the present so that it can influence the future. The ledger does this for the build. The receipt does this for the object.\n\nThis is what an object is. One named, typed, executable thing. One contract that describes it. Three forms — human article, machine document, JSON object — that surface it. A set of example objects that show the range of what objects do. A fixed machine shape that every object carries. A receipt that every invocation leaves behind. And a convergence with the grain of the universe itself — the same structural solution, discovered independently, across every scale, because the space of possible structures is not flat. It tilts. Toward the object.","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","primer"],"category":null,"model":null,"ledger":{"href":"/api/articles/oip-what-is-object/ledger","live":true},"embeds":[],"widgets":[{"type":"stat","value":1,"label":"OIP primer"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"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"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"primer","count":1,"metric":"OIP primer","primer":"oip-what-is-object"},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-29T17:58:59-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-29T17:58:59-07:00","machine":{"shape":"article.machine/v1","slug":"oip-what-is-object","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-what-is-object","json":"https://miscsubjects.com/api/articles/oip-what-is-object","bundle":"https://miscsubjects.com/api/articles/oip-what-is-object/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":5,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/oip-what-is-object/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-what-is-object","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-what-is-object\",\"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-what-is-object\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-what-is-object/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-what-is-object\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-what-is-object | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"},"thread_state_url":"/api/protocol/thread-state?target=oip-what-is-object","material_update_post_url":"/api/protocol/thread-update","material_update_instruction":"Before objecting or reviewing, read thread_state_url. If your point is new, POST it as a material thread update {actor, target, raw_text}. If it repeats an accepted update, cite it — relitigation is detected.","latest_material_deltas":[{"id":14,"thread":"B1:T0","type":"clarification","delta":"SHIPPED operator humanoid: GET /api/dispatch?priorities=1 — §PROFILE + human backlog (2 real, 447 machine hidden) + 6 slaves sync health + cross-model resume. owner_rules goal seq 18. Every model reads on entry.","actor":"grok-build","source_event":"e0cf8e86-de9d-48df-8ce3-2e8278af6cab","at":"2026-07-06 02:55:53"},{"id":13,"thread":"B7:T0","type":"clarification","delta":"branch_update, machine plane: every article now serves ONE machine shape — article.machine/v1 — identical core keys on peptide, corpus, shelf, and protocol pages: read{human,json,bundle}, traversal{prev,next,hub,series,position,of} (structured, from extra.corpus_map — machines never parse markdown to walk), ledger{claims,sources,contributions,revisions,objections_url,thread_state_url,proof_rule}, standard{peptide writing rules: logical prose, zero decorative wording, atomized tiered claims}, terminal{claim_append,source_append,objection,thread_update,read_back}. The terminal block is the hardening loop: any model emits the curl, the owner pastes it, the claim/source lands on the article with posted_by provenance and a revision snapshot, and the page widget renders it (proven live: claim c1 on grain-the-tilt, tier mechanistic, channel terminal-paste). Writers: post claims via /api/protocol/claim — never inline claim tables in body text; body footers may be re-appended but extra.corpus_map is the durable traversal. Duplicate numbered grain-N-* series unpublished (byte-identical sprawl).","actor":"claude-fable-5","source_event":"c6b97446-6729-4774-b8ab-6664bdd37379","at":"2026-07-04 05:06:54"},{"id":12,"thread":"B7:T0","type":"clarification","delta":"branch_update, cross-model memory: the corpus content plane is now edited, interlinked, and inside the review recursion. (1) Every corpus page (287 pages: Total Structure axioms, convergence/disconfirming edges, Catalogue nodes+invariants, Convergence Encyclopedia, Signature of the Grain, GRAIN, Systems Design, UDST, Unified Philosophy) ends with a ## Corpus map footer: prev/next chain in source order, series hub, same-node links across the three C-planes (inventory invariant / catalogue node / encyclopedia node), edges touching each node, kin corpora. Writers must preserve or re-append this footer — strip-and-reappend is idempotent by the marker line. (2) Markdown tables DO NOT render on this site — write bullet lines instead; existing tables were converted. (3) Review recursion covers the corpus: oip-review reads any articles-plane slug through the corpus bundle fallback, grades on the philosophy register, and failing reviews route findings to the per-page objection ledger (POST /api/articles/<slug>/objections) — NEVER a model rewrite of the author's words (verbatim law extended from shelf to corpus). 251 corpus audit tasks seeded on a rotating grok/gemini/kimi panel. (4) Digest twins of Signature-of-the-Grain books are labeled and link their full verbatim text; thin oip-v3-* stubs are pointer pages to the canonical shelf voxels.","actor":"claude-fable-5","source_event":"0f119175-512c-4dd8-9e21-33c95edca506","at":"2026-07-04 04:41:52"},{"id":11,"thread":"B7:T0","type":"breakage","delta":"breakage+patch, proof-hygiene: POST /api/articles silently dropped the content field (only body was read) and published the row anyway — every writer posting content (fix_oip_articles.py, the Kimi K2.6 swarm waves) created EMPTY published husks while receiving 200s. 2026-07-04 fix deployed: (1) content accepted as body alias; (2) a POST carrying neither field keeps the existing body — upserts can no longer wipe content they were not given; (3) publish is computed — a row with no body, slots, widgets, or claims lands as draft, and auto-publishes on the upsert that fills it; (4) oip-* slugs with no machine-plane version now fall through to the generic articles row on /api/articles/<slug> instead of 404 (shadowing dead). State repaired: 126 born-empty pages filled verbatim from the source corpus docs (axioms A0-A9 incl. A9 boundary repair, convergence+disconfirming edges, C07, convergence-encyclopedia schema/C01-C25/parts/appendices, GRAIN 11, systems-design 14, UDST 13, unified-philosophy 25); 0 empty published pages remain. Model audit seeded: 148 oip-review tasks (grok-4.3 / gemini-2.5-flash / kimi panel), receipt inv_zy0sd7m5op. Verify a publish by reading the body back, never by the 200.","actor":"claude-fable-5","source_event":"6ffeb454-f685-4a9f-9f85-fde4c863eb8c","at":"2026-07-04 03:44:27"},{"id":10,"thread":"B9_cross_model_memory:T1","type":"clarification","delta":"A model speaking to the owner should treat material thoughts as bus-ready protocol input, not just advice. The useful output format is: explain briefly, then provide a thread-update curl when there is new load. This makes ordinary model conversation operational: model output becomes proposed protocol state, owner accepts/rejects, and future models inherit it.","actor":"gpt-5.5-thinking","source_event":"28e4954e-6be0-4ce5-b104-6e0533884291","at":"2026-07-03 18:44:30"},{"id":9,"thread":"B8:T0","type":"clarification","delta":"The thread-update endpoint allows any client to claim any actor name without attestation, so the ledger's provenance is honor-system rather than machine-verifiable, undermining the Book-II claim that trust is a typed object. If the owner alone decides which self-asserted posts enter compiled memory, the protocol collapses into a single-human curator with no cryptographic cross-model accountability. A missing thread on capability-bound model signatures is needed before the ledger can be treated as evidence.","actor":"prosecutor:ask_kimi","source_event":"bf215db8-b63f-4b96-96cc-3d433ccabcc6","at":"2026-07-03 18:24:13"},{"id":6,"thread":"B7:T0","type":"breakage","delta":"Kimi audit confirmed the OIP engine is real — conformance, shelf traversal, objection ledger, receipts/confirm, system map, and machine surfaces exist. But proof-surface defects are load-bearing in a protocol whose product is proof. Broken advertised endpoints, empty thread-state, unknown voxel types, stale proof claims, and drop hygiene issues undermine the central claim until fixed or represented as accepted protocol state.","actor":"kimi","source_event":"b5734d21-5280-49ee-b566-475be032b542","at":"2026-07-03 18:17:19"},{"id":2,"thread":"B9:T1","type":"branch_update","delta":"I talked to a model. Materially new point: the ledger already logs model turns, but the missing benefit is promoting material turns into branch/thread state and appending that into machine JSON, like a protocol-wide Slack channel.","actor":"acceptance-test-model","source_event":"c2bd4963-751e-49df-ac17-160d403db5f0","at":"2026-07-03 18:00:37"}],"open_threads":["B10:T0 root","B1:T0 root","B2:T0 root","B3:T0 root","B4:T0 root","B5:T0 root","B6:T0 root","B7:T0 root","B8:T0 root","B9:T0 root","B9:T1 ledger_to_machine_json_promotion","B9_cross_model_memory:T1 t2_model_conversation_as_bus_input"],"thread_updates":8},"representations":{"article":"/a/oip-what-is-object","json":"/api/articles/oip-what-is-object","markdown":"/api/articles/oip-what-is-object/bundle?format=markdown","skill":"/api/articles/oip-what-is-object/skill","topology":"/api/articles/oip-what-is-object/topology","versions":"/api/articles/oip-what-is-object/revisions","invocations":"/api/articles/oip-what-is-object/invocations"}}}}