## §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 > FLOW > FLOW_CANDIDATES
**Capability:** `FLOW_CANDIDATES` — Procedures the ledger has watched succeed repeatedly: traces grouped by their ordered capability sequence, with counts, example trace ids and which steps carry side effects. Evidence that a stable procedure exists and a FLOW_LEARN line for each.
**When to use:** you want to know what the build keeps doing by hand that could be compiled.
**RUN NOW (open this URL):** https://miscsubjects.com/api/dispatch?invoke=FLOW_CANDIDATES&body=30%7C3&share=<TOKEN>
**Example call:** [FLOW_CANDIDATES]30|3[/FLOW_CANDIDATES]
- **type · runner:** tool · edge · learned
- **run it:** Open run_now (URL, fires the example), or POST https://miscsubjects.com/api/dispatch {"key":"FLOW_CANDIDATES","body":"30|3"}. From the router: [FLOW_CANDIDATES]30|3[/FLOW_CANDIDATES]
- **inputs:** {"type":"object","properties":{"days_min":{"type":"string","description":"days|min_repeats (pipe position 1)"}},"required":["days_min"],"x-arg-order":["days_min"],"description":"Arguments are joined with | in the order given by x-arg-order."}
- **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
### 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=FLOW_CANDIDATES&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=FLOW&format=markdown
- append-only ledger: https://miscsubjects.com/api/invocations?object_id=FLOW_CANDIDATES
- receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>
- replay: POST /api/dispatch {"replay":"inv_ID"}
- repair: POST /api/dispatch {"key":"FLOW_CANDIDATES","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=FLOW_CANDIDATES
- **argument/body mismatch** — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=FLOW_CANDIDATES
- **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=FLOW_CANDIDATES
2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [FLOW_CANDIDATES]args[/FLOW_CANDIDATES]. → 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=FLOW_CANDIDATES
4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=Procedures%20the%20ledger%20has%20watched%20succee
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=FLOW_CANDIDATES
- **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.*