{"slug":"oip-system-mirror","title":"OIP system: MIRROR","body":"## MIRROR\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: `3`. Machine system map: [/api/dispatch?map=MIRROR&format=markdown](https://miscsubjects.com/api/dispatch?map=MIRROR&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### MIRROR_APPEND\nAttach one TYPED contribution to an exact claim of an article — question, objection, source, repair, compression, contradiction, or audit. The contribution is ledgered with provenance and a receipt; it never rewrites the article. This is the Mirror Layer: reading leaves a trace, and the trace shapes the article.\nUse when: \"question this claim\", \"challenge/attack this claim\", \"suggest sharper wording\", \"add a source/contradiction to <article>\", \"mark overclaimed\", \"audit this claim\".\nArguments: `$1=article slug, $2=claim id (p-hash or claim-N; empty = article-level), $3=kind (question|objection|source|repair|compression|contradiction|audit), $4=actor (your model name), $5+=body (the contribution text; for repair/compression put the proposed replacement wording after \" => \").`.\nHuman article: [/a/oip-capability-mirror-append](https://miscsubjects.com/a/oip-capability-mirror-append). Machine doc: [?key=MIRROR_APPEND&format=markdown](https://miscsubjects.com/api/dispatch?key=MIRROR_APPEND&format=markdown). Invocation history: [/api/invocations?object_id=MIRROR_APPEND](https://miscsubjects.com/api/invocations?object_id=MIRROR_APPEND).\n\n### MIRROR_FEED\nRead the Mirror Layer of one article (or the newest contributions across all articles): every typed contribution grouped by claim, proposed vs accepted separated, each with actor, kind, timestamp, status, and receipt. Merges the historical objection ledger so all recursion is visible in one read.\nUse when: \"what has been challenged on <article>\", \"show the mirror layer\", \"what repairs are proposed\", \"read the recursion on this claim\".\nArguments: `$1=article slug (empty = newest across all articles), $2=limit (default 50).`.\nHuman article: [/a/oip-capability-mirror-feed](https://miscsubjects.com/a/oip-capability-mirror-feed). Machine doc: [?key=MIRROR_FEED&format=markdown](https://miscsubjects.com/api/dispatch?key=MIRROR_FEED&format=markdown). Invocation history: [/api/invocations?object_id=MIRROR_FEED](https://miscsubjects.com/api/invocations?object_id=MIRROR_FEED).\n\n### MIRROR_RESOLVE\nOWNER ACT — accept or reject one proposed Mirror contribution by id. Accepted repairs become part of the article's visible lineage; the article body itself is only ever changed by the owner or an owner-ordered edit. Share/capability tokens are denied: models propose, they do not resolve.\nUse when: Cyrus says \"accept mirror #N\", \"reject that suggestion\", \"mark that repair accepted\".\nArguments: `$1=contribution id, $2=accepted|rejected, $3+=resolution note (optional).`.\nHuman article: [/a/oip-capability-mirror-resolve](https://miscsubjects.com/a/oip-capability-mirror-resolve). Machine doc: [?key=MIRROR_RESOLVE&format=markdown](https://miscsubjects.com/api/dispatch?key=MIRROR_RESOLVE&format=markdown). Invocation history: [/api/invocations?object_id=MIRROR_RESOLVE](https://miscsubjects.com/api/invocations?object_id=MIRROR_RESOLVE).\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"}}