{"slug":"oip-capability-design-law","title":"OIP capability: DESIGN_LAW","body":"## DESIGN_LAW\n\nThis is one executable OIP object. It is the leaf where prose stops and exact invocation begins.\n\nDiscover the canonical Laws of Design Knowledge-Action Object.\\n# WHEN_TO_USE: any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n\nParent system: [DESIGN](https://miscsubjects.com/api/dispatch?map=DESIGN&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip). Machine doc: [/api/dispatch?key=DESIGN_LAW&format=markdown](https://miscsubjects.com/api/dispatch?key=DESIGN_LAW&format=markdown). Invocation history: [/api/invocations?object_id=DESIGN_LAW](https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW).\n\n## Invoke\n\nExample: `[DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.`\n\nRun URL: `https://miscsubjects.com/api/dispatch?invoke=DESIGN_LAW&share=<TOKEN>`\n\nAuth: `none`. Risk: `low`.\n\n## Machine contract\n\n- Read this article first; do not infer the row shape from memory.\n- If acting with a URL-only tool, open run_now after replacing placeholder args.\n- If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.\n- If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.\n\n## Troubleshooting\n\n- **unknown key** - Use the did_you_mean links or ask URL; never guess another key.\n- **argument/body mismatch** - Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes.\n- **expired or corrupted token** - Report token_expired/token_corrupted from the response; owner mints a fresh scoped link.\n- **tool returned ok:false / exit nonzero** - Do not call it sent. Read the receipt, correct the body, fire a repair.\n\n## Receipt loop\n\nAfter any action, open the receipt. If it is wrong, repair it with `POST /api/dispatch {key, body, repairs:\"inv_ID\"}`. If you need to repeat the exact recorded call, replay it with `POST /api/dispatch {replay:\"inv_ID\"}`.\n\n## Full generated capability doc\n\n## §SELF — miscsubjects capability (paste without context)\n**Principle:** Self-explaining payload — no external context required. This _self block is the capability: what it is, how to run it, how to change it, and where to look next.\n**Path:** OIP > DESIGN > DESIGN_LAW\n**Capability:** `DESIGN_LAW` — Discover the canonical Laws of Design Knowledge-Action Object.\\n# WHEN_TO_USE: any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n**When to use:** any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n**RUN NOW (open this URL):** https://miscsubjects.com/api/dispatch?invoke=DESIGN_LAW&share=<TOKEN>\n**Example call:** [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n- **type · runner:** tool · http · design\n- **run it:** POST https://miscsubjects.com/api/dispatch {\"key\":\"DESIGN_LAW\",\"body\":\"<args>\"}  ·  from the router: [DESIGN_LAW]args[/DESIGN_LAW]\n- **inputs:** {\"args\":\"none for the contract; follow representations.invoke with surface and task to apply it.\\\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\"}\n- **outputs:** { ok, result, invocation, yield, _self } — result is this object's output; yield is tokens/cost/material; invocation is the ledgered record.\n- **auth · risk:** none · low\n### Machine Contract\n- Read this article first; do not infer the row shape from memory.\n- If acting with a URL-only tool, open run_now after replacing placeholder args.\n- If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.\n- If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.\n### Invocation, Ledger, Repair\n- root tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown\n- parent system article: https://miscsubjects.com/api/dispatch?map=DESIGN&format=markdown\n- append-only ledger: https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW\n- receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>\n- replay: POST /api/dispatch {\"replay\":\"inv_ID\"}\n- repair: POST /api/dispatch {\"key\":\"DESIGN_LAW\",\"body\":\"corrected args\",\"repairs\":\"inv_ID\"}\n### Troubleshooting\n- **unknown key** — Use the did_you_mean links or ask URL; never guess another key. · https://miscsubjects.com/api/dispatch?ask=DESIGN_LAW\n- **argument/body mismatch** — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=DESIGN_LAW\n- **expired or corrupted token** — Report token_expired/token_corrupted from the response; owner mints a fresh scoped link. · https://miscsubjects.com/api/dispatch?explain=1&share=<TOKEN>\n- **tool returned ok:false / exit nonzero** — Do not call it sent. Read the receipt, correct the body, fire a repair. · https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>\n### Logical proof (verify each step)\n1. Every capability is an invokable object with its own _self — this block. → https://miscsubjects.com/api/dispatch?key=DESIGN_LAW\n2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [DESIGN_LAW]args[/DESIGN_LAW]. → https://miscsubjects.com/api/dispatch?registry=1\n3. Every invocation is ledgered with actor, cost, and material/waste. → https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW\n4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=Discover%20the%20canonical%20Laws%20of%20Design%20Kn\n5. The whole build is one self-describing map, with the terminal key. → https://miscsubjects.com/api/dispatch?build=1\n### Where to look next\n- **registry** — Every capability, self-describing · https://miscsubjects.com/api/dispatch?registry=1\n- **ask** — Ask the build what to use, in plain language · https://miscsubjects.com/api/dispatch?ask=<question>\n- **history** — This capability's invocation history — its edges · https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW\n- **build** — The whole build as one map (terminal key) · https://miscsubjects.com/api/dispatch?build=1\n*Self-explaining. Not project knowledge — fetch specifics from the links above.*","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","capability"],"model":null,"ledger":null,"embeds":[],"widgets":[{"type":"stat","value":1,"label":"capability"},{"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":"capability","count":1,"key":"DESIGN_LAW","metric":"capability"},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-17T23:11:44-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-17T23:11:44-07:00","machine":{"shape":"article.machine/v1","slug":"oip-capability-design-law","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-capability-design-law","json":"https://miscsubjects.com/api/articles/oip-capability-design-law","bundle":"https://miscsubjects.com/api/articles/oip-capability-design-law/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-capability-design-law/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-capability-design-law","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-capability-design-law\",\"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-capability-design-law\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-capability-design-law/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-capability-design-law\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-capability-design-law | 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-capability-design-law","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-capability-design-law","json":"/api/articles/oip-capability-design-law","markdown":"/api/articles/oip-capability-design-law/bundle?format=markdown","skill":"/api/articles/oip-capability-design-law/skill","topology":"/api/articles/oip-capability-design-law/topology","versions":"/api/articles/oip-capability-design-law/revisions","invocations":"/api/articles/oip-capability-design-law/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-capability-design-law","slug":"oip-capability-design-law","title":"OIP capability: DESIGN_LAW"},"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-capability-design-law","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-capability-design-law/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-capability-design-law\ndescription: Apply the OIP capability: DESIGN_LAW article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# OIP capability: DESIGN_LAW\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-capability-design-law). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-capability-design-law.\n- Read claims and relationships at /api/articles/oip-capability-design-law/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\nDESIGN LAW This is one executable OIP object. It is the leaf where prose stops and exact invocation begins. Discover the canonical Laws of Design Knowledge-Action Object.\\n WHEN TO USE: any design, rendering, navigation, editorial, graph, a\n\n## Representations\n\n- Human: /a/oip-capability-design-law\n- JSON: /api/articles/oip-capability-design-law\n- Relationships: /api/articles/oip-capability-design-law/topology\n- History: /api/articles/oip-capability-design-law/revisions\n"},"json":{"route":"/api/articles/oip-capability-design-law","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-capability-design-law/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"CF_API_GAPS","type":"fn","target":"cfApiGaps","category":"capability","enabled":true,"contract":"# WHAT: Analyze the CF row target_map. Returns counts, known namespaces, expected namespaces, missing namespaces, coverage_pct\n# WHEN_TO_USE: you need to cf api gaps\n# ARGS: none\n# EX: [CF_API_GAPS][/CF_API_GAPS]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CF_API_GAPS","json":"/api/directory/CF_API_GAPS","skill":"/api/directory/CF_API_GAPS?format=skill","oip_contract":"/api/dispatch?key=CF_API_GAPS"}},{"key":"OIP_TREE","type":"http","target":"GET https://miscsubjects.com/api/dispatch?map=1&format=markdown","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":"TEST_ALL","type":"fn","target":"testAll","category":"capability","enabled":true,"contract":"# WHAT: Run TEST_ROW on every key that has a directory_tests entry. $1=limit (default 50). Returns {run_id, keys, passed, failed, summary[]}\n# WHEN_TO_USE: you need to test all\n# ARGS: $1\n# EX: [TEST_ALL]arg1[/TEST_ALL]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/TEST_ALL","json":"/api/directory/TEST_ALL","skill":"/api/directory/TEST_ALL?format=skill","oip_contract":"/api/dispatch?key=TEST_ALL"}},{"key":"DISCOVER_SOURCE","type":"fn","target":"discoverSource","category":"capability","enabled":true,"contract":"# WHAT: Fetch a public URL (API docs, OpenAPI spec, GitHub raw, vendor SDK readme) and persist the raw body to R2 under capability_sources/<sha16>.txt. Returns {url, bytes, r2_key, sha256_16, status}. First step of universe-to-row. $1=URL\n# WHEN_TO_USE: you need to discover source\n# ARGS: $1\n# EX: [DISCOVER_SOURCE]arg1[/DISCOVER_SOURCE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/DISCOVER_SOURCE","json":"/api/directory/DISCOVER_SOURCE","skill":"/api/directory/DISCOVER_SOURCE?format=skill","oip_contract":"/api/dispatch?key=DISCOVER_SOURCE"}},{"key":"EXTRACT_CAPABILITIES","type":"fn","target":"extractCapabilities","category":"capability","enabled":true,"contract":"# WHAT: Given an R2 key from DISCOVER_SOURCE, run a Workers AI Llama call to extract a JSON array of {op, method, url_or_signature,  Truncates input at 20KB. Second step of universe-to-row. $1=r2_key, $2=optional model id (default @cf/meta/llama-3.3-70b-instruct-fp8-fast)\n# WHEN_TO_USE: you need to extract capabilities\n# ARGS: [{name,type,required}], description}\n# EX: [EXTRACT_CAPABILITIES]arg1|arg2[/EXTRACT_CAPABILITIES]\n[\"$1\",\"$2\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/EXTRACT_CAPABILITIES","json":"/api/directory/EXTRACT_CAPABILITIES","skill":"/api/directory/EXTRACT_CAPABILITIES?format=skill","oip_contract":"/api/dispatch?key=EXTRACT_CAPABILITIES"}},{"key":"GAP_REPORT","type":"fn","target":"gapReport","category":"capability","enabled":true,"contract":"# WHAT: Given the same shape as PROPOSE_ROWS, diff the discovered ops against existing directory keys. Returns {ops_total, found, missing, missing_ops[]}. Surfaces what is genuinely new\n# WHEN_TO_USE: you need to gap report\n# ARGS: $1\n# EX: [GAP_REPORT]arg1[/GAP_REPORT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GAP_REPORT","json":"/api/directory/GAP_REPORT","skill":"/api/directory/GAP_REPORT?format=skill","oip_contract":"/api/dispatch?key=GAP_REPORT"}},{"key":"PROPOSE_ROWS","type":"fn","target":"proposeRows","category":"capability","enabled":true,"contract":"# WHAT: Given the JSON output of EXTRACT_CAPABILITIES (raw JSON string OR an r2_key starting with capability_sources/), emit SQL INSERTs for new directory rows, one per discovered op. Rows land disabled + planner_visible=0 so the owner can review before activating. $1=ops_json_or_r2_key, $2=category prefix (default \"discovered\")\n# WHEN_TO_USE: you need to propose rows\n# ARGS: $1 | $2\n# EX: [PROPOSE_ROWS]arg1|arg2[/PROPOSE_ROWS]\n[\"$1\",\"$2\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/PROPOSE_ROWS","json":"/api/directory/PROPOSE_ROWS","skill":"/api/directory/PROPOSE_ROWS?format=skill","oip_contract":"/api/dispatch?key=PROPOSE_ROWS"}},{"key":"TEST_ROW","type":"fn","target":"testRow","category":"capability","enabled":true,"contract":"# WHAT: Run every directory_tests row for the given KEY against /api/dispatch, score against expect_kind/expect_value, append rows to fidelity_log under one run_id. $1=KEY. Returns {key, run_id, total, passed, failed, results[]}\n# WHEN_TO_USE: you need to test row\n# ARGS: $1\n# EX: [TEST_ROW]arg1[/TEST_ROW]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/TEST_ROW","json":"/api/directory/TEST_ROW","skill":"/api/directory/TEST_ROW?format=skill","oip_contract":"/api/dispatch?key=TEST_ROW"}},{"key":"ARXIV_GROW","type":"fn","target":"arxivGrow","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","target":"arxivState","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","target":"capMint","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","target":"githubTail","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","target":"oipReceipt","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","target":"oipRepair","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","target":"oipReplay","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","target":"capExplain","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","target":"capRevoke","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"}},{"key":"AGENT_IMPORT","type":"fn","target":"agentImport","category":"capability","enabled":true,"contract":"# WHAT: Cannibalize an agent definition (md frontmatter name/description/model/tools) into a proposed agent row. PROPOSE only\n# WHEN_TO_USE: you need to agent import\n# ARGS: source(url|r2:key|raw)|category\n# EX: [AGENT_IMPORT]arg1|arg2[/AGENT_IMPORT]\n[\"$1\",\"$2\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/AGENT_IMPORT","json":"/api/directory/AGENT_IMPORT","skill":"/api/directory/AGENT_IMPORT?format=skill","oip_contract":"/api/dispatch?key=AGENT_IMPORT"}},{"key":"MCP_IMPORT","type":"fn","target":"mcpImport","category":"capability","enabled":true,"contract":"# WHAT: Cannibalize an MCP server: read its tools/list and emit a proposed directory row per tool (GAP-checked vs existing keys). PROPOSE only — returns SQL; apply with D1_EXEC or wrangler\n# WHEN_TO_USE: you need to mcp import\n# ARGS: server_url|category|auth_env_var\n# EX: [MCP_IMPORT]arg1|arg2|arg3[/MCP_IMPORT]\n[\"$1\",\"$2\",\"$3\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/MCP_IMPORT","json":"/api/directory/MCP_IMPORT","skill":"/api/directory/MCP_IMPORT?format=skill","oip_contract":"/api/dispatch?key=MCP_IMPORT"}},{"key":"SKILL_IMPORT","type":"fn","target":"skillImport","category":"capability","enabled":true,"contract":"# WHAT: Cannibalize a SKILL.md (frontmatter name+description, markdown body) into a proposed agent row. PROPOSE only\n# WHEN_TO_USE: you need to skill import\n# ARGS: source(url|r2:key|raw)|model|category\n# EX: [SKILL_IMPORT]arg1|arg2|arg3[/SKILL_IMPORT]\n[\"$1\",\"$2\",\"$3\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/SKILL_IMPORT","json":"/api/directory/SKILL_IMPORT","skill":"/api/directory/SKILL_IMPORT?format=skill","oip_contract":"/api/dispatch?key=SKILL_IMPORT"}},{"key":"DESIGN_LAW","type":"http","target":"GET https://miscsubjects.com/api/articles/design-law","category":"design","enabled":true,"contract":"# WHAT: Discover the canonical Laws of Design Knowledge-Action Object.\\n# WHEN_TO_USE: any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/DESIGN_LAW","json":"/api/directory/DESIGN_LAW","skill":"/api/directory/DESIGN_LAW?format=skill","oip_contract":"/api/dispatch?key=DESIGN_LAW"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","object-invocation-protocol","protocol-specification","machine-native-json","capability","oip","capability","design","law"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-capability-design-law/invocations?status=success","failure_events":"/api/articles/oip-capability-design-law/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-capability-design-law","title":"OIP capability: DESIGN_LAW","body":"## DESIGN_LAW\n\nThis is one executable OIP object. It is the leaf where prose stops and exact invocation begins.\n\nDiscover the canonical Laws of Design Knowledge-Action Object.\\n# WHEN_TO_USE: any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n\nParent system: [DESIGN](https://miscsubjects.com/api/dispatch?map=DESIGN&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip). Machine doc: [/api/dispatch?key=DESIGN_LAW&format=markdown](https://miscsubjects.com/api/dispatch?key=DESIGN_LAW&format=markdown). Invocation history: [/api/invocations?object_id=DESIGN_LAW](https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW).\n\n## Invoke\n\nExample: `[DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.`\n\nRun URL: `https://miscsubjects.com/api/dispatch?invoke=DESIGN_LAW&share=<TOKEN>`\n\nAuth: `none`. Risk: `low`.\n\n## Machine contract\n\n- Read this article first; do not infer the row shape from memory.\n- If acting with a URL-only tool, open run_now after replacing placeholder args.\n- If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.\n- If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.\n\n## Troubleshooting\n\n- **unknown key** - Use the did_you_mean links or ask URL; never guess another key.\n- **argument/body mismatch** - Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes.\n- **expired or corrupted token** - Report token_expired/token_corrupted from the response; owner mints a fresh scoped link.\n- **tool returned ok:false / exit nonzero** - Do not call it sent. Read the receipt, correct the body, fire a repair.\n\n## Receipt loop\n\nAfter any action, open the receipt. If it is wrong, repair it with `POST /api/dispatch {key, body, repairs:\"inv_ID\"}`. If you need to repeat the exact recorded call, replay it with `POST /api/dispatch {replay:\"inv_ID\"}`.\n\n## Full generated capability doc\n\n## §SELF — miscsubjects capability (paste without context)\n**Principle:** Self-explaining payload — no external context required. This _self block is the capability: what it is, how to run it, how to change it, and where to look next.\n**Path:** OIP > DESIGN > DESIGN_LAW\n**Capability:** `DESIGN_LAW` — Discover the canonical Laws of Design Knowledge-Action Object.\\n# WHEN_TO_USE: any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n**When to use:** any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n**RUN NOW (open this URL):** https://miscsubjects.com/api/dispatch?invoke=DESIGN_LAW&share=<TOKEN>\n**Example call:** [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\n- **type · runner:** tool · http · design\n- **run it:** POST https://miscsubjects.com/api/dispatch {\"key\":\"DESIGN_LAW\",\"body\":\"<args>\"}  ·  from the router: [DESIGN_LAW]args[/DESIGN_LAW]\n- **inputs:** {\"args\":\"none for the contract; follow representations.invoke with surface and task to apply it.\\\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.\"}\n- **outputs:** { ok, result, invocation, yield, _self } — result is this object's output; yield is tokens/cost/material; invocation is the ledgered record.\n- **auth · risk:** none · low\n### Machine Contract\n- Read this article first; do not infer the row shape from memory.\n- If acting with a URL-only tool, open run_now after replacing placeholder args.\n- If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.\n- If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.\n### Invocation, Ledger, Repair\n- root tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown\n- parent system article: https://miscsubjects.com/api/dispatch?map=DESIGN&format=markdown\n- append-only ledger: https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW\n- receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>\n- replay: POST /api/dispatch {\"replay\":\"inv_ID\"}\n- repair: POST /api/dispatch {\"key\":\"DESIGN_LAW\",\"body\":\"corrected args\",\"repairs\":\"inv_ID\"}\n### Troubleshooting\n- **unknown key** — Use the did_you_mean links or ask URL; never guess another key. · https://miscsubjects.com/api/dispatch?ask=DESIGN_LAW\n- **argument/body mismatch** — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=DESIGN_LAW\n- **expired or corrupted token** — Report token_expired/token_corrupted from the response; owner mints a fresh scoped link. · https://miscsubjects.com/api/dispatch?explain=1&share=<TOKEN>\n- **tool returned ok:false / exit nonzero** — Do not call it sent. Read the receipt, correct the body, fire a repair. · https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>\n### Logical proof (verify each step)\n1. Every capability is an invokable object with its own _self — this block. → https://miscsubjects.com/api/dispatch?key=DESIGN_LAW\n2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [DESIGN_LAW]args[/DESIGN_LAW]. → https://miscsubjects.com/api/dispatch?registry=1\n3. Every invocation is ledgered with actor, cost, and material/waste. → https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW\n4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=Discover%20the%20canonical%20Laws%20of%20Design%20Kn\n5. The whole build is one self-describing map, with the terminal key. → https://miscsubjects.com/api/dispatch?build=1\n### Where to look next\n- **registry** — Every capability, self-describing · https://miscsubjects.com/api/dispatch?registry=1\n- **ask** — Ask the build what to use, in plain language · https://miscsubjects.com/api/dispatch?ask=<question>\n- **history** — This capability's invocation history — its edges · https://miscsubjects.com/api/invocations?object_id=DESIGN_LAW\n- **build** — The whole build as one map (terminal key) · https://miscsubjects.com/api/dispatch?build=1\n*Self-explaining. Not project knowledge — fetch specifics from the links above.*","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","capability"],"model":null,"ledger":null,"embeds":[],"widgets":[{"type":"stat","value":1,"label":"capability"},{"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":"capability","count":1,"key":"DESIGN_LAW","metric":"capability"},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-17T23:11:44-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-17T23:11:44-07:00","machine":{"shape":"article.machine/v1","slug":"oip-capability-design-law","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-capability-design-law","json":"https://miscsubjects.com/api/articles/oip-capability-design-law","bundle":"https://miscsubjects.com/api/articles/oip-capability-design-law/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-capability-design-law/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-capability-design-law","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-capability-design-law\",\"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-capability-design-law\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-capability-design-law/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-capability-design-law\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-capability-design-law | 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-capability-design-law","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-capability-design-law","json":"/api/articles/oip-capability-design-law","markdown":"/api/articles/oip-capability-design-law/bundle?format=markdown","skill":"/api/articles/oip-capability-design-law/skill","topology":"/api/articles/oip-capability-design-law/topology","versions":"/api/articles/oip-capability-design-law/revisions","invocations":"/api/articles/oip-capability-design-law/invocations"}}}}