## §OIP SYSTEM ARTICLE — X (5 operations)
A 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.

### Read Order
- scan operations
- open a leaf doc
- run via run_now or POST /api/dispatch
- open receipt
- repair/replay if needed

### Operations
- **X_SEARCH** — 
  doc: https://miscsubjects.com/api/dispatch?key=X_SEARCH&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=X_SEARCH&body=%3Carg1%3E&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=X_SEARCH
- **X_POST** — Publish one exact plain-text post to X as @CannibalCapital through OAuth user context.
  when: Use when the current person explicitly asks to post, OR after substantive work under the owner's full-act ecosystem-proof edit drop. That dr
  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.
  doc: https://miscsubjects.com/api/dispatch?key=X_POST&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=X_POST&body=%3Cexact%20plain%20post%20text%3E&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=X_POST
- **X_REPLY** — Post ONE reply to a specific tweet as the account (same OAuth1 creds as X_POST).
  when: only when the owner directs a reply to a specific tweet, under the owner rules. Single-target; not autonomous mass-replying.
  args: $1=in_reply_to tweet id or status URL | $2=reply text (<=280)
  doc: https://miscsubjects.com/api/dispatch?key=X_REPLY&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=X_REPLY&body=%3Cin_reply_to%20tweet%20id%20or%20stat%3E%7C%3Creply%20text%3E&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=X_REPLY
- **X_DELETE** — Delete ONE tweet the account published (DELETE /2/tweets/:id, same OAuth1 creds as X_POST).
  when: the owner directs a post to be removed, or a post that violated the format law must be retracted. Owner-directed only — never autonomous tim
  args: $1 = tweet id or full status URL
  doc: https://miscsubjects.com/api/dispatch?key=X_DELETE&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=X_DELETE&body=2080749124673302742&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=X_DELETE
- **X_WHOAMI** — Report which X credentials are present and what X says about them (GET /2/users/me).
  when: X_POST or X_DELETE returns 401/403 and you need the real cause instead of a bare "Unauthorized".
  args: none
  doc: https://miscsubjects.com/api/dispatch?key=X_WHOAMI&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=X_WHOAMI&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=X_WHOAMI

### Troubleshooting
- If a row's example has placeholders, replace only the placeholder values and preserve separators.
- If a call fails, open its receipt and repair it with POST /api/dispatch {key, body, repairs:'inv_ID'}.
- If token scope denies this system, ask the owner for a row:/rows:/pfx: token scoped to the exact operation set.

Back to the tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown