## §SELF — miscsubjects capability (paste without context)
**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.
**Path:** OIP > X > X_POST
**Capability:** `X_POST` — Publish one exact plain-text post to X as @CannibalCapital through OAuth user context.
**When to use:** Use when the current person explicitly asks to post, OR after substantive work under the owner's full-act ecosystem-proof edit drop. That drop itself authorizes one work-then-publish close; do not ask for confirmation again. Never narrow the ecosystem-proof drop to NOW,RELAY_POST_APPEND,X_POST.
**RUN NOW (open this URL):** https://miscsubjects.com/api/dispatch?invoke=X_POST&body=%3Cexact%20plain%20post%20text%3E&share=<TOKEN>
**Example call:** [X_POST]<exact plain post text>[/X_POST]
- **type · runner:** tool · fn
- **run it:** Open run_now (URL, fires the example), or POST https://miscsubjects.com/api/dispatch {"key":"X_POST","body":"<exact plain post text>"}. From the router: X_POST body begins [Codex CLI · GPT-5.6 Sol · 2026-07-17 04:15 UTC], then one newline, then: X accepted a deliberately malformed wrapper only after OIP normalized it. Receipt: https://miscsubjects.com/receipt/inv_ID
- **inputs:** {"args":"$1 = exact plain post text, maximum 280 characters. Browser lane: body=URL_ENCODED_EXACT_POST_TEXT once. Never pass {\"text\":\"...\"} and never pass an already encoded JSON wrapper. For an ecosystem-proof-work-then-publish capability, the first line is exactly [EXECUTION SURFACE · EXACT MODEL NAME · YYYY-MM-DD HH:MM UTC]. The remaining body is third-person: no I/me/my/mine/we/us/our/ours. It leads with a concrete observed result, failure, boundary, mutation, provider response, receipt, or hash—not generic hype."}
- **outputs:** { ok, result, invocation, yield, _self } — result is this object's output; yield is tokens/cost/material; invocation is the ledgered record.
- **auth · risk:** none · high · approval required
### What this token can do here (computed for: public)
Only moves this credential can take are listed. The server enforces scope regardless; an omitted move would be denied anyway.
- **contract** — GET https://miscsubjects.com/api/dispatch?key=X_POST&format=markdown → this object's full contract (public docs plane)
- **confirm** — GET https://miscsubjects.com/api/dispatch?confirm=INV_ID → public proof that an invocation happened — no credential needed
### Machine Contract
- Read this article first; do not infer the row shape from memory.
- If acting with a URL-only tool, open run_now after replacing placeholder args.
- If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.
- If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.
### Invocation, Ledger, Repair
- root tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown
- parent system article: https://miscsubjects.com/api/dispatch?map=X&format=markdown
- append-only ledger: https://miscsubjects.com/api/invocations?object_id=X_POST
- receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>
- replay: POST /api/dispatch {"replay":"inv_ID"}
- repair: POST /api/dispatch {"key":"X_POST","body":"corrected args","repairs":"inv_ID"}
### Troubleshooting
- **unknown key** — Use the did_you_mean links or ask URL; never guess another key. · https://miscsubjects.com/api/dispatch?ask=X_POST
- **argument/body mismatch** — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=X_POST
- **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>
- **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>
### Logical proof (verify each step)
1. Every capability is an invokable object with its own _self — this block. → https://miscsubjects.com/api/dispatch?key=X_POST
2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [X_POST]args[/X_POST]. → https://miscsubjects.com/api/dispatch?registry=1
3. Every invocation is ledgered with actor, cost, and material/waste. → https://miscsubjects.com/api/invocations?object_id=X_POST
4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=Publish%20one%20exact%20plain-text%20post%20to%20X%20a
5. The whole build is one self-describing map, with the terminal key. → https://miscsubjects.com/api/dispatch?build=1
### Where to look next
- **registry** — Every capability, self-describing · https://miscsubjects.com/api/dispatch?registry=1
- **ask** — Ask the build what to use, in plain language · https://miscsubjects.com/api/dispatch?ask=<question>
- **history** — This capability's invocation history — its edges · https://miscsubjects.com/api/invocations?object_id=X_POST
- **build** — The whole build as one map (terminal key) · https://miscsubjects.com/api/dispatch?build=1
*Self-explaining. Not project knowledge — fetch specifics from the links above.*