## §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 > ALLOCATE > ALLOCATE_REASONING
**Capability:** `ALLOCATE_REASONING` — The runtime allocator. Turns an action and its action class into R (loss exposure), K (complexity) and epsilon (permitted wrongful-action rate) from a VERSIONED SERVER-OWNED policy, selects the least-cost configuration whose MEASURED undetected-wrong rate is at or below that epsilon, executes it so every model payload lands on the ledger, seals it with SEAL_PANEL bound to those records, and then performs the bounded downstream act only if the seal returns APPROVE. NEGATE refuses the act. NO_ACTION leaves it untouched. DISPUTE and ESCALATE create a human-review object bound to a NAMED reviewer 
**When to use:** any consequential action that must not execute until enough auditable reasoning has been purchased for its consequence.
**RUN NOW (open this URL):** https://miscsubjects.com/api/dispatch?invoke=ALLOCATE_REASONING&body=%7B%22action%22%3A%22file%20the%20clause%20(c)%20notice%22%2C%22action_class%22%3A%22board-authority%22%2C%22question%22%3A%22Does%20this%20engage%20the%20notification%20duty%3F%22%2C%22ruleset_hash%22%3A%220df47944...%22%2C%22rules%22%3A%5B%22...%22%5D%2C%22artifact%22%3A%22...%22%2C%22artifact_hash%22%3A%228c689258...%22%2C%22reviewer%22%3A%22Jane%20Roe%2C%20audit%20committee%20chair%22%7D&share=<TOKEN>
**Example call:** [ALLOCATE_REASONING]{"action":"file the clause (c) notice","action_class":"board-authority","question":"Does this engage the notification duty?","ruleset_hash":"0df47944...","rules":["..."],"artifact":"...","artifact_hash":"8c689258...","reviewer":"Jane Roe, audit committee chair"}[/ALLOCATE_REASONING]
- **type · runner:** tool · fn · adjudication
- **run it:** Open run_now (URL, fires the example), or POST https://miscsubjects.com/api/dispatch {"key":"ALLOCATE_REASONING","body":"{"action":"file the clause (c) notice","action_class":"board-authority","question":"Does this engage the notification duty?","ruleset_hash":"0df47944...","rules":["..."],"artifact":"...","artifact_hash":"8c689258...","reviewer":"Jane Roe, audit committee chair"}"}. From the router: [ALLOCATE_REASONING]{"action":"file the clause (c) notice","action_class":"board-authority","question":"Does this engage the notification duty?","ruleset_hash":"0df47944...","rules":["..."],"artifact":"...","artifact_hash":"8c689258...","reviewer":"Jane Roe, audit committee chair"}[/ALLOCATE_REASONING]
- **inputs:** {"type":"object","required":["action","action_class","question","ruleset_hash","rules","artifact_hash"],"properties":{"action":{"type":"string"},"action_class":{"enum":["formatting","internal-bookkeeping","statutory-applicability","board-authority","pre-trade-control","clinical-finding"]},"question":{"type":"string"},"ruleset_url":{"type":"string"},"ruleset_hash":{"type":"string"},"rules":{"type":"array"},"artifact":{"type":"string"},"artifact_hash":{"type":"string"},"task_class":{"type":"string"},"reviewer":{"type":"string"},"reviewer_audience":{"type":"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 · 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=ALLOCATE_REASONING&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=ALLOCATE&format=markdown
- append-only ledger: https://miscsubjects.com/api/invocations?object_id=ALLOCATE_REASONING
- receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>
- replay: POST /api/dispatch {"replay":"inv_ID"}
- repair: POST /api/dispatch {"key":"ALLOCATE_REASONING","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=ALLOCATE_REASONING
- **argument/body mismatch** — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=ALLOCATE_REASONING
- **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=ALLOCATE_REASONING
2. You run it by POSTing to /api/dispatch; in a model turn the router tag is [ALLOCATE_REASONING]args[/ALLOCATE_REASONING]. → 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=ALLOCATE_REASONING
4. You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=The%20runtime%20allocator.%20Turns%20an%20action%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=ALLOCATE_REASONING
- **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.*