OIP capability: DELIVER_PENDING_ASSETS

DELIVER_PENDING_ASSETS

This is one executable OIP object. It is the leaf where prose stops and exact invocation begins.

Trigger the durable Workflow that drains pending_deliveries. Equivalent to the old /api/deliver heartbeat but with native retries and observability. WHEN_TO_USE: "drain the pending deliveries" or "force a deliver pass"

Parent system: DELIVER. Root: /a/oip. Machine doc: /api/dispatch?key=DELIVER_PENDING_ASSETS&format=markdown. Invocation history: /api/invocations?object_id=DELIVER_PENDING_ASSETS.

Invoke

Example: [DELIVER_PENDING_ASSETS][/DELIVER_PENDING_ASSETS]

Run URL: https://miscsubjects.com/api/dispatch?invoke=DELIVER_PENDING_ASSETS&share=<TOKEN>

Auth: none. Risk: low.

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.

Troubleshooting

• unknown key - Use the did_you_mean links or ask URL; never guess another key.
• argument/body mismatch - Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes.
• expired or corrupted token - Report token_expired/token_corrupted from the response; owner mints a fresh scoped link.
• tool returned ok:false / exit nonzero - Do not call it sent. Read the receipt, correct the body, fire a repair.

Receipt loop

After 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"}.

Full generated capability doc

§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 > DELIVER > DELIVER_PENDING_ASSETS Capability: DELIVER_PENDING_ASSETS — Trigger the durable Workflow that drains pending_deliveries. Equivalent to the old /api/deliver heartbeat but with native retries and observability. WHEN_TO_USE: "drain the pending deliveries" or "force a deliver pass" When to use: "drain the pending deliveries" or "force a deliver pass" RUN NOW (open this URL): https://miscsubjects.com/api/dispatch?invoke=DELIVER_PENDING_ASSETS&share=<TOKEN> Example call: [DELIVER_PENDING_ASSETS][/DELIVER_PENDING_ASSETS]

• type · runner: workflow · edge · flow
• run it: POST https://miscsubjects.com/api/dispatch {"key":"DELIVER_PENDING_ASSETS","body":"<args>"} · from the router: [DELIVER_PENDING_ASSETS]args[/DELIVER_PENDING_ASSETS]
• inputs: {"body":"pipe-delimited args e.g. \"a|b\"; single arg = the value itself; no args = empty string"}
• 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 · low

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=DELIVER&format=markdown
• append-only ledger: https://miscsubjects.com/api/invocations?object_id=DELIVER_PENDING_ASSETS
• receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>
• replay: POST /api/dispatch {"replay":"inv_ID"}
• repair: POST /api/dispatch {"key":"DELIVER_PENDING_ASSETS","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=DELIVER_PENDING_ASSETS
• argument/body mismatch — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=DELIVER_PENDING_ASSETS
• 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=DELIVER_PENDING_ASSETS
2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [DELIVER_PENDING_ASSETS]args[/DELIVER_PENDING_ASSETS]. → 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=DELIVER_PENDING_ASSETS
4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=DELIVER_PENDING_ASSETS
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=DELIVER_PENDING_ASSETS
• 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.