{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"oip-system-x","title":"OIP system: X","body":"## X\n\nA generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.\n\nThis page is the operating article for one build subsystem. It is generated from live directory rows. If a task belongs to this subsystem, scan the operations below, open the matching capability article, run only the exact object named there, and verify by receipt.\n\nKind: `core`. Capabilities: `5`. Machine system map: [/api/dispatch?map=X&format=markdown](https://miscsubjects.com/api/dispatch?map=X&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### X_SEARCH\nInvokable OIP capability.\nHuman article: [/a/oip-capability-x-search](https://miscsubjects.com/a/oip-capability-x-search). Machine doc: [?key=X_SEARCH&format=markdown](https://miscsubjects.com/api/dispatch?key=X_SEARCH&format=markdown). Invocation history: [/api/invocations?object_id=X_SEARCH](https://miscsubjects.com/api/invocations?object_id=X_SEARCH).\n\n### X_POST\nPublish one exact plain-text post to X as @CannibalCapital through OAuth user context.\nUse when: Use when the current person explicitly asks to post, OR after substantive work under the owner's full-act ecosystem-proof edit drop. That drop itself authorizes one work-then-publish close; do not ask for confirmation again. Never narrow the ecosystem-proof drop to NOW,RELAY_POST_APPEND,X_POST.\nArguments: `$1 = exact plain post text, maximum 280 characters. Browser lane: body=URL_ENCODED_EXACT_POST_TEXT once. Never pass {\"text\":\"...\"} and never pass an already encoded JSON wrapper. For an ecosystem-proof-work-then-publish capability, the first line is exactly [EXECUTION SURFACE · EXACT MODEL NAME · YYYY-MM-DD HH:MM UTC]. The remaining body is third-person: no I/me/my/mine/we/us/our/ours. It leads with a concrete observed result, failure, boundary, mutation, provider response, receipt, or hash—not generic hype.`.\nHuman article: [/a/oip-capability-x-post](https://miscsubjects.com/a/oip-capability-x-post). Machine doc: [?key=X_POST&format=markdown](https://miscsubjects.com/api/dispatch?key=X_POST&format=markdown). Invocation history: [/api/invocations?object_id=X_POST](https://miscsubjects.com/api/invocations?object_id=X_POST).\n\n### X_REPLY\nPost ONE reply to a specific tweet as the account (same OAuth1 creds as X_POST).\nUse when: only when the owner directs a reply to a specific tweet, under the owner rules. Single-target; not autonomous mass-replying.\nArguments: `$1=in_reply_to tweet id or status URL | $2=reply text (<=280)`.\nHuman article: [/a/oip-capability-x-reply](https://miscsubjects.com/a/oip-capability-x-reply). Machine doc: [?key=X_REPLY&format=markdown](https://miscsubjects.com/api/dispatch?key=X_REPLY&format=markdown). Invocation history: [/api/invocations?object_id=X_REPLY](https://miscsubjects.com/api/invocations?object_id=X_REPLY).\n\n### X_DELETE\nDelete ONE tweet the account published (DELETE /2/tweets/:id, same OAuth1 creds as X_POST).\nUse when: the owner directs a post to be removed, or a post that violated the format law must be retracted. Owner-directed only — never autonomous timeline pruning.\nArguments: `$1 = tweet id or full status URL`.\nHuman article: [/a/oip-capability-x-delete](https://miscsubjects.com/a/oip-capability-x-delete). Machine doc: [?key=X_DELETE&format=markdown](https://miscsubjects.com/api/dispatch?key=X_DELETE&format=markdown). Invocation history: [/api/invocations?object_id=X_DELETE](https://miscsubjects.com/api/invocations?object_id=X_DELETE).\n\n### X_WHOAMI\nReport which X credentials are present and what X says about them (GET /2/users/me).\nUse when: X_POST or X_DELETE returns 401/403 and you need the real cause instead of a bare \"Unauthorized\".\nArguments: `none`.\nHuman article: [/a/oip-capability-x-whoami](https://miscsubjects.com/a/oip-capability-x-whoami). Machine doc: [?key=X_WHOAMI&format=markdown](https://miscsubjects.com/api/dispatch?key=X_WHOAMI&format=markdown). Invocation history: [/api/invocations?object_id=X_WHOAMI](https://miscsubjects.com/api/invocations?object_id=X_WHOAMI).\n","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","system"],"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"}}