OIP capability: CREATIVE_GENERATE
CREATIVE_GENERATE
This is one executable OIP object. It is the leaf where prose stops and exact invocation begins.
Generate one explicitly owner-requested image/video version while preserving its exact payload, raw response, channel, R2 result, and parent lineage in creative_runs.
Parent system: CREATIVE. Root: /a/oip. Machine doc: /api/dispatch?key=CREATIVE_GENERATE&format=markdown. Invocation history: /api/invocations?object_id=CREATIVE_GENERATE.
Invoke
Example: [CREATIVE_GENERATE]{"engine":"grok","prompt":"exact prompt"}[/CREATIVE_GENERATE]
Run URL: https://miscsubjects.com/api/dispatch?invoke=CREATIVE_GENERATE&body=%7B%22engine%22%3A%22grok%22%2C%22prompt%22%3A%22exact%20prompt%22%7D&share=<TOKEN>
Auth: none. Risk: high.
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 > CREATIVE > CREATIVE_GENERATE Capability: CREATIVE_GENERATE — Generate one explicitly owner-requested image/video version while preserving its exact payload, raw response, channel, R2 result, and parent lineage in creative_runs. RUN NOW (open this URL): https://miscsubjects.com/api/dispatch?invoke=CREATIVE_GENERATE&body=%7B%22engine%22%3A%22grok%22%2C%22prompt%22%3A%22exact%20prompt%22%7D&share=<TOKEN> Example call: [CREATIVE_GENERATE]{"engine":"grok","prompt":"exact prompt"}[/CREATIVE_GENERATE]
- type · runner: tool · fn · creative
- run it: Open run_now (URL, fires the example), or POST https://miscsubjects.com/api/dispatch {"key":"CREATIVE_GENERATE","body":"{"engine":"grok","prompt":"exact prompt"}"}. From the router: [CREATIVE_GENERATE]{"engine":"grok","prompt":"exact prompt"}[/CREATIVE_GENERATE]
- inputs: {"args":"one JSON object: {engine,prompt,model?,size?,aspect_ratio?,reference_url?,duration?,resolution?,product_id?,enhance?}. engine=openai|grok|arcads-image|arcads-video."}
- 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
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=CREATIVE&format=markdown
- append-only ledger: https://miscsubjects.com/api/invocations?object_id=CREATIVE_GENERATE
- receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>
- replay: POST /api/dispatch {"replay":"inv_ID"}
- repair: POST /api/dispatch {"key":"CREATIVE_GENERATE","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=CREATIVE_GENERATE
- argument/body mismatch — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=CREATIVE_GENERATE
- 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)
- Every capability is an invokable object with its own _self — this block. → https://miscsubjects.com/api/dispatch?key=CREATIVE_GENERATE
- You run it by POSTing to /api/dispatch; in a model turn the router tag is [CREATIVE_GENERATE]args[/CREATIVE_GENERATE]. → https://miscsubjects.com/api/dispatch?registry=1
- Every invocation is ledgered with actor, cost, and material/waste. → https://miscsubjects.com/api/invocations?object_id=CREATIVE_GENERATE
- You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=Generate%20one%20explicitly%20owner-requested%20
- 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=CREATIVE_GENERATE
- 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.