{"slug":"oip-capability-leads-draft-ai","title":"OIP capability: LEADS_DRAFT_AI","body":"## LEADS_DRAFT_AI\n\nThis is one executable OIP object. It is the leaf where prose stops and exact invocation begins.\n\nGrok writes the outreach email for a lead, grounded in the OUTREACH_DOSSIER (brand, team, offer, article+store links) and the lead's real site context. Saves the draft. DOES NOT SEND.\n\nParent system: [LEADS](https://miscsubjects.com/api/dispatch?map=LEADS&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip). Machine doc: [/api/dispatch?key=LEADS_DRAFT_AI&format=markdown](https://miscsubjects.com/api/dispatch?key=LEADS_DRAFT_AI&format=markdown). Invocation history: [/api/invocations?object_id=LEADS_DRAFT_AI](https://miscsubjects.com/api/invocations?object_id=LEADS_DRAFT_AI).\n\n## Invoke\n\nExample: `[LEADS_DRAFT_AI]131|LeoResearch[/LEADS_DRAFT_AI]`\n\nRun URL: `https://miscsubjects.com/api/dispatch?invoke=LEADS_DRAFT_AI&body=131%7CLeoResearch&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 > LEADS > LEADS_DRAFT_AI\n**Capability:** `LEADS_DRAFT_AI` — Grok writes the outreach email for a lead, grounded in the OUTREACH_DOSSIER (brand, team, offer, article+store links) and the lead's real site context. Saves the draft. DOES NOT SEND.\n**When to use:** draft a real, personalized email instead of the plain template.\n**RUN NOW (open this URL):** https://miscsubjects.com/api/dispatch?invoke=LEADS_DRAFT_AI&body=131%7CLeoResearch&share=<TOKEN>\n**Example call:** [LEADS_DRAFT_AI]131|LeoResearch[/LEADS_DRAFT_AI]\n- **type · runner:** tool · fn · biz-dev\n- **run it:** Open run_now (URL, fires the example), or POST https://miscsubjects.com/api/dispatch {\"key\":\"LEADS_DRAFT_AI\",\"body\":\"131|LeoResearch\"}. From the router: [LEADS_DRAFT_AI]131|LeoResearch[/LEADS_DRAFT_AI]\n- **inputs:** {\"args\":\"$1 = lead id, $2 = brand (default LeoResearch).\"}\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=LEADS&format=markdown\n- append-only ledger: https://miscsubjects.com/api/invocations?object_id=LEADS_DRAFT_AI\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\":\"LEADS_DRAFT_AI\",\"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=LEADS_DRAFT_AI\n- **argument/body mismatch** — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=LEADS_DRAFT_AI\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=LEADS_DRAFT_AI\n2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [LEADS_DRAFT_AI]args[/LEADS_DRAFT_AI]. → 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=LEADS_DRAFT_AI\n4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=Grok%20writes%20the%20outreach%20email%20for%20a%20lea\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=LEADS_DRAFT_AI\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":"LEADS_DRAFT_AI","metric":"capability"},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-06T02:25:49-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-06T02:25:49-07:00","machine":{"shape":"article.machine/v1","slug":"oip-capability-leads-draft-ai","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-capability-leads-draft-ai","json":"https://miscsubjects.com/api/articles/oip-capability-leads-draft-ai","bundle":"https://miscsubjects.com/api/articles/oip-capability-leads-draft-ai/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-leads-draft-ai/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-capability-leads-draft-ai","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-leads-draft-ai\",\"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-leads-draft-ai\",\"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-leads-draft-ai/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-leads-draft-ai\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-capability-leads-draft-ai | 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-leads-draft-ai","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}}