{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"udst-v1-1-appendix-c-attack-types","title":"UDST: V1 1 Appendix C Attack Types","body":"# Appendix C — Attack Types\n\n1. **Definition** — terms are incoherent. In the build, this is tested by the `?ask` endpoint: if a term cannot be resolved to a capability, the router returns `did_you_mean` with nearest keys. A term that has no nearest key is incoherent. Example: asking for `LOCAL_BATTERY` when the capability is `LOCAL_BATTERY` (not `LOCAL_BATTERY_CHECK`) — the router returns `did_you_mean: [LOCAL_BATTERY]` and the term is resolved. A term that returns no nearest keys is flagged as a definition error.\n\n2. **Logic** — conclusion does not follow. In the build, this is tested by the materiality classifier: `POST /api/protocol/thread-update` classifies the raw turn into `objection`, `settlement`, `patch`, `breakage`, `test_result`, `clarification`, `prior_art`, `open_question`, or `branch_update`. If the conclusion does not follow from the premises, the classifier routes it to `sludge` (noise floor), not `material`. The logic is tested by the ledger: if the conclusion contradicts the premises in the same thread, the owner rejects it.\n\n3. **Empirical** — a real case falsifies. In the build, this is tested by the conformance suite: `GET /api/dispatch?conformance=1` runs 15 clauses against production, each with a live receipt. An empirical attack must produce a receipt that shows the clause failing. A claim without a receipt is not empirical.\n\n4. **Scope** — full-scope accounting is impossible or misused. In the build, this is tested by the receipt's `story` field: the story is a one-line forensic narrative that includes the full accounting (enforcement cost, externality, recurrence, suppressed capability, downstream instability, maintenance burden, audit debt). A receipt without a story is out of scope. The `?receipt=INV_ID` endpoint returns the full story; if the story omits a known cost, the scope is violated.\n\n5. **Category-error** — a concept is transferred across levels invalidly. In the build, this is tested by the capability's `category` field: a capability is typed by category (e.g., `oip`, `mcp`, `system`, `runner`), and a concept from one category cannot be transferred to another without explicit mapping. Example: treating `OIP` as a content management protocol (category `content`) when it is an object invocation protocol (category `oip`) is a category error. The directory enforces category boundaries.\n\n6. **Implementation** — the protocol cannot be executed. In the build, this is tested by the `?conformance=1` endpoint: if any clause cannot be executed, the suite returns `status: failed` with the exact clause and error. The protocol is not a specification; it is a live system that executes every time it is invoked.\n\n7. **Prior-art** — the welded construction already exists. In the build, this is tested by the `?why=1` endpoint: it lists 18 objections, each with a verdict. If the attack is already addressed, the endpoint returns the settled answer and the relitigation detection. The system does not claim novelty; it claims operationality.\n\n8. **Falsifiability** — the counterexample condition cannot be met in practice. In the build, this is tested by the `?conformance=1` endpoint: the falsifiers are live metrics, not theoretical conditions. If a counterexample cannot be produced, the system does not claim it is impossible; it claims it has not been observed. The ledger records the absence of counterexamples as a standing metric.\n\nA valid attack states its type, names its tier, names the exact claim, shows the work, and proposes the minimum patch. In the build, this is the `POST /api/protocol/thread-update` endpoint: the body must include `type`, `tier`, `exact_claim`, `work`, and `minimum_patch`. If any field is missing, the classifier routes it to `sludge`. The system does not reject attacks; it classifies them. Valid attacks are material; invalid attacks are noise. The distinction is not censorship; it is taxonomy.\n\n\n---\n\n## Corpus map\n- Previous: [UDST: V1 1 Appendix B Compact Benchmark](/a/udst-v1-1-appendix-b-compact-benchmark)\n- Series start: [UDST v1.1 — The Claim](/a/udst-v1-1-the-claim)\n- Kin: [Book V — The Machine Plane](/a/oip-v3-book-v-the-machine-plane) · [Total Structure](/a/oip-total-structure)","hero":null,"images":[],"style":{},"tags":["OIP","UDST","systems-theory","deterministic"],"category":null,"model":"Fable 5 (Claude Code)","ledger":{"href":"/api/articles/udst-v1-1-appendix-c-attack-types/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"text":"The build tests definition errors via the ?ask endpoint: a term that returns no nearest keys is flagged as incoherent.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Definition attack type."},{"text":"The materiality classifier at POST /api/protocol/thread-update routes conclusions that do not follow from premises to sludge, not material.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Logic attack type."},{"text":"An empirical attack must produce a receipt showing clause failure; a claim without a receipt is not empirical.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Empirical attack type."},{"text":"A receipt without a story field is out of scope; the ?receipt=INV_ID endpoint returns the full forensic narrative.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Scope attack type."},{"text":"The directory enforces category boundaries via the capability's category field; transferring a concept across categories without explicit mapping is a category error.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Category-error attack type."},{"text":"A valid attack submitted to POST /api/protocol/thread-update must include type, tier, exact_claim, work, and minimum_patch; missing fields route to sludge.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from final paragraph of Appendix C on valid attack structure."}],"sources":[{"type":"system","url":"https://miscsubjects.com/api/dispatch?conformance=1","title":"Build Conformance Suite","quote":"GET /api/dispatch?conformance=1 runs 15 clauses against production, each with a live receipt.","summary":"Live endpoint executing 15 conformance clauses with receipts."},{"type":"system","url":"https://miscsubjects.com/api/protocol/thread-update","title":"Materiality Classifier","quote":"POST /api/protocol/thread-update classifies the raw turn into objection, settlement, patch, breakage, test_result, clarification, prior_art, open_question, or branch_update.","summary":"Open intake endpoint classifying material turns and routing invalid attacks to sludge."},{"type":"article","url":"https://miscsubjects.com/a/udst-v1-1-the-claim","title":"UDST v1.1 — The Claim","quote":"A valid attack states its type, names its tier, names the exact claim, shows the work, and proposes the minimum patch.","summary":"Hub article defining valid attack structure for the UDST v1.1 series."},{"type":"system","url":"https://miscsubjects.com/api/dispatch?why=1","title":"Prior Art & Objections Endpoint","quote":"The ?why=1 endpoint lists 18 objections, each with a verdict.","summary":"Endpoint enumerating settled objections with verdicts for relitigation detection."}],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":"udst-v1-1-appendix-b-compact-benchmark","next":null,"hub":"udst-v1-1-the-claim","series":"udst-v1-1","position":13,"of":13}},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":7,"contributions":[],"provenance":[{"ts":"2026-07-04T03:40:09.782Z","model":"claude-fable-5","action":"fill","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"0b06640a9912b127921ba184bc7a3abb04deb69419c67020d29f982326184ddb"},{"ts":"2026-07-04T04:39:11.316Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"0b06640a9912b127921ba184bc7a3abb04deb69419c67020d29f982326184ddb","hash":"4275adf4de1bba86790d5ef0ffa1e6789b9a08a13ac717e26298d1c663fee57c"},{"ts":"2026-07-04T05:03:15.628Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"4275adf4de1bba86790d5ef0ffa1e6789b9a08a13ac717e26298d1c663fee57c","hash":"feb76dfc01da4bc3a7aa7020bd93e35596d827b24176172dc07ac3f206c44595"},{"ts":"2026-07-17T02:37:51.187Z","model":"owner","action":"voxel_divide","prompt":"","input":"udst-v1-1-appendix-c-attack-types","response":"13 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"feb76dfc01da4bc3a7aa7020bd93e35596d827b24176172dc07ac3f206c44595","hash":"e46379bbcae0b65f398bd14eec0b84af64279047dc85abe3b090fb32f83d3b4b"},{"ts":"2026-08-06T09:30:35.255Z","model":"unknown","action":"edit","why":"the nine books are published under canonical oip-v3-book-<numeral> slugs while the corpus maps link short slugs that never existed; the pages were not missing, the addresses were wrong","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"e46379bbcae0b65f398bd14eec0b84af64279047dc85abe3b090fb32f83d3b4b","hash":"d3f8f55b4525c948179db01735c8e32c1607c54506df161e82cea1e09fb2e0b7"}],"energy":{"passes":5,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5":3,"owner":1,"unknown":1},"head":"d3f8f55b4525c948179db01735c8e32c1607c54506df161e82cea1e09fb2e0b7"},"posted_at":"2026-07-04T03:17:54.012Z","created_at":"2026-07-04T03:17:54.012Z","updated_at":"2026-08-06T09:30:35.255Z","machine":{"shape":"article.machine/v1","slug":"udst-v1-1-appendix-c-attack-types","kind":"corpus","read":{"human":"https://miscsubjects.com/a/udst-v1-1-appendix-c-attack-types","json":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types","bundle":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/bundle?format=markdown"},"traversal":{"prev":{"slug":"udst-v1-1-appendix-b-compact-benchmark","human":"https://miscsubjects.com/a/udst-v1-1-appendix-b-compact-benchmark","json":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-b-compact-benchmark"},"next":null,"hub":{"slug":"udst-v1-1-the-claim","human":"https://miscsubjects.com/a/udst-v1-1-the-claim","json":"https://miscsubjects.com/api/articles/udst-v1-1-the-claim"},"series":"udst-v1-1","position":13,"of":13},"ledger":{"claims":6,"sources":4,"contributions":0,"revisions":7,"objections_url":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=udst-v1-1-appendix-c-attack-types","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":"source text is prose-preserving — attack via objections, never rewrite the author's words"},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"udst-v1-1-appendix-c-attack-types\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"udst-v1-1-appendix-c-attack-types\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"udst-v1-1-appendix-c-attack-types\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/udst-v1-1-appendix-c-attack-types","json":"/api/articles/udst-v1-1-appendix-c-attack-types","markdown":"/api/articles/udst-v1-1-appendix-c-attack-types/bundle?format=markdown","skill":"/api/articles/udst-v1-1-appendix-c-attack-types/skill","topology":"/api/articles/udst-v1-1-appendix-c-attack-types/topology","versions":"/api/articles/udst-v1-1-appendix-c-attack-types/revisions","invocations":"/api/articles/udst-v1-1-appendix-c-attack-types/invocations"},"editorial_review":null,"editorial_audit":{"slug":"udst-v1-1-appendix-c-attack-types","ok":false,"issues":[{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"1ee442c99a4ff7ae872e4175013ee3c054496fa12c11befe86698f10b3f790fe","object":{"object_type":"article-object","identity":{"id":"article:udst-v1-1-appendix-c-attack-types","slug":"udst-v1-1-appendix-c-attack-types","title":"UDST: V1 1 Appendix C Attack Types"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/udst-v1-1-appendix-c-attack-types","role":"explain","audience":"human"},"skill":{"route":"/api/articles/udst-v1-1-appendix-c-attack-types/skill","role":"direct behavior","audience":"model","content":"---\nname: udst-v1-1-appendix-c-attack-types\ndescription: Apply the UDST: V1 1 Appendix C Attack Types article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# UDST: V1 1 Appendix C Attack Types\n\nThis Skill is the behavioral expression of [the canonical article](/a/udst-v1-1-appendix-c-attack-types). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/udst-v1-1-appendix-c-attack-types.\n- Read claims and relationships at /api/articles/udst-v1-1-appendix-c-attack-types/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nAppendix C — Attack Types 1. Definition — terms are incoherent. In the build, this is tested by the ?ask endpoint: if a term cannot be resolved to a capability, the router returns did you mean with nearest keys. A term that has no nearest k\n\n## Representations\n\n- Human: /a/udst-v1-1-appendix-c-attack-types\n- JSON: /api/articles/udst-v1-1-appendix-c-attack-types\n- Relationships: /api/articles/udst-v1-1-appendix-c-attack-types/topology\n- History: /api/articles/udst-v1-1-appendix-c-attack-types/revisions\n"},"json":{"route":"/api/articles/udst-v1-1-appendix-c-attack-types","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/udst-v1-1-appendix-c-attack-types/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: the owner or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: the owner says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.the owner.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/[OWNER_HANDLE]/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: the owner asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: the owner says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/[OWNER_HANDLE]/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: the owner asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: the owner asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: the owner says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: the owner says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: the owner asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: the owner says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["OIP","UDST","systems-theory","deterministic","udst","v1","1","appendix","c","attack","types"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/udst-v1-1-appendix-c-attack-types/invocations?status=success","failure_events":"/api/articles/udst-v1-1-appendix-c-attack-types/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"udst-v1-1-appendix-c-attack-types","title":"UDST: V1 1 Appendix C Attack Types","body":"# Appendix C — Attack Types\n\n1. **Definition** — terms are incoherent. In the build, this is tested by the `?ask` endpoint: if a term cannot be resolved to a capability, the router returns `did_you_mean` with nearest keys. A term that has no nearest key is incoherent. Example: asking for `LOCAL_BATTERY` when the capability is `LOCAL_BATTERY` (not `LOCAL_BATTERY_CHECK`) — the router returns `did_you_mean: [LOCAL_BATTERY]` and the term is resolved. A term that returns no nearest keys is flagged as a definition error.\n\n2. **Logic** — conclusion does not follow. In the build, this is tested by the materiality classifier: `POST /api/protocol/thread-update` classifies the raw turn into `objection`, `settlement`, `patch`, `breakage`, `test_result`, `clarification`, `prior_art`, `open_question`, or `branch_update`. If the conclusion does not follow from the premises, the classifier routes it to `sludge` (noise floor), not `material`. The logic is tested by the ledger: if the conclusion contradicts the premises in the same thread, the owner rejects it.\n\n3. **Empirical** — a real case falsifies. In the build, this is tested by the conformance suite: `GET /api/dispatch?conformance=1` runs 15 clauses against production, each with a live receipt. An empirical attack must produce a receipt that shows the clause failing. A claim without a receipt is not empirical.\n\n4. **Scope** — full-scope accounting is impossible or misused. In the build, this is tested by the receipt's `story` field: the story is a one-line forensic narrative that includes the full accounting (enforcement cost, externality, recurrence, suppressed capability, downstream instability, maintenance burden, audit debt). A receipt without a story is out of scope. The `?receipt=INV_ID` endpoint returns the full story; if the story omits a known cost, the scope is violated.\n\n5. **Category-error** — a concept is transferred across levels invalidly. In the build, this is tested by the capability's `category` field: a capability is typed by category (e.g., `oip`, `mcp`, `system`, `runner`), and a concept from one category cannot be transferred to another without explicit mapping. Example: treating `OIP` as a content management protocol (category `content`) when it is an object invocation protocol (category `oip`) is a category error. The directory enforces category boundaries.\n\n6. **Implementation** — the protocol cannot be executed. In the build, this is tested by the `?conformance=1` endpoint: if any clause cannot be executed, the suite returns `status: failed` with the exact clause and error. The protocol is not a specification; it is a live system that executes every time it is invoked.\n\n7. **Prior-art** — the welded construction already exists. In the build, this is tested by the `?why=1` endpoint: it lists 18 objections, each with a verdict. If the attack is already addressed, the endpoint returns the settled answer and the relitigation detection. The system does not claim novelty; it claims operationality.\n\n8. **Falsifiability** — the counterexample condition cannot be met in practice. In the build, this is tested by the `?conformance=1` endpoint: the falsifiers are live metrics, not theoretical conditions. If a counterexample cannot be produced, the system does not claim it is impossible; it claims it has not been observed. The ledger records the absence of counterexamples as a standing metric.\n\nA valid attack states its type, names its tier, names the exact claim, shows the work, and proposes the minimum patch. In the build, this is the `POST /api/protocol/thread-update` endpoint: the body must include `type`, `tier`, `exact_claim`, `work`, and `minimum_patch`. If any field is missing, the classifier routes it to `sludge`. The system does not reject attacks; it classifies them. Valid attacks are material; invalid attacks are noise. The distinction is not censorship; it is taxonomy.\n\n\n---\n\n## Corpus map\n- Previous: [UDST: V1 1 Appendix B Compact Benchmark](/a/udst-v1-1-appendix-b-compact-benchmark)\n- Series start: [UDST v1.1 — The Claim](/a/udst-v1-1-the-claim)\n- Kin: [Book V — The Machine Plane](/a/oip-v3-book-v-the-machine-plane) · [Total Structure](/a/oip-total-structure)","hero":null,"images":[],"style":{},"tags":["OIP","UDST","systems-theory","deterministic"],"category":null,"model":"Fable 5 (Claude Code)","ledger":{"href":"/api/articles/udst-v1-1-appendix-c-attack-types/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"text":"The build tests definition errors via the ?ask endpoint: a term that returns no nearest keys is flagged as incoherent.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Definition attack type."},{"text":"The materiality classifier at POST /api/protocol/thread-update routes conclusions that do not follow from premises to sludge, not material.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Logic attack type."},{"text":"An empirical attack must produce a receipt showing clause failure; a claim without a receipt is not empirical.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Empirical attack type."},{"text":"A receipt without a story field is out of scope; the ?receipt=INV_ID endpoint returns the full forensic narrative.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Scope attack type."},{"text":"The directory enforces category boundaries via the capability's category field; transferring a concept across categories without explicit mapping is a category error.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from Appendix C prose on Category-error attack type."},{"text":"A valid attack submitted to POST /api/protocol/thread-update must include type, tier, exact_claim, work, and minimum_patch; missing fields route to sludge.","tier":"runtime","source_ids":[],"who_claims":"normandy-repair","rationale":"Derived from final paragraph of Appendix C on valid attack structure."}],"sources":[{"type":"system","url":"https://miscsubjects.com/api/dispatch?conformance=1","title":"Build Conformance Suite","quote":"GET /api/dispatch?conformance=1 runs 15 clauses against production, each with a live receipt.","summary":"Live endpoint executing 15 conformance clauses with receipts."},{"type":"system","url":"https://miscsubjects.com/api/protocol/thread-update","title":"Materiality Classifier","quote":"POST /api/protocol/thread-update classifies the raw turn into objection, settlement, patch, breakage, test_result, clarification, prior_art, open_question, or branch_update.","summary":"Open intake endpoint classifying material turns and routing invalid attacks to sludge."},{"type":"article","url":"https://miscsubjects.com/a/udst-v1-1-the-claim","title":"UDST v1.1 — The Claim","quote":"A valid attack states its type, names its tier, names the exact claim, shows the work, and proposes the minimum patch.","summary":"Hub article defining valid attack structure for the UDST v1.1 series."},{"type":"system","url":"https://miscsubjects.com/api/dispatch?why=1","title":"Prior Art & Objections Endpoint","quote":"The ?why=1 endpoint lists 18 objections, each with a verdict.","summary":"Endpoint enumerating settled objections with verdicts for relitigation detection."}],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":"udst-v1-1-appendix-b-compact-benchmark","next":null,"hub":"udst-v1-1-the-claim","series":"udst-v1-1","position":13,"of":13}},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":7,"contributions":[],"provenance":[{"ts":"2026-07-04T03:40:09.782Z","model":"claude-fable-5","action":"fill","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"0b06640a9912b127921ba184bc7a3abb04deb69419c67020d29f982326184ddb"},{"ts":"2026-07-04T04:39:11.316Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"0b06640a9912b127921ba184bc7a3abb04deb69419c67020d29f982326184ddb","hash":"4275adf4de1bba86790d5ef0ffa1e6789b9a08a13ac717e26298d1c663fee57c"},{"ts":"2026-07-04T05:03:15.628Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"4275adf4de1bba86790d5ef0ffa1e6789b9a08a13ac717e26298d1c663fee57c","hash":"feb76dfc01da4bc3a7aa7020bd93e35596d827b24176172dc07ac3f206c44595"},{"ts":"2026-07-17T02:37:51.187Z","model":"owner","action":"voxel_divide","prompt":"","input":"udst-v1-1-appendix-c-attack-types","response":"13 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"feb76dfc01da4bc3a7aa7020bd93e35596d827b24176172dc07ac3f206c44595","hash":"e46379bbcae0b65f398bd14eec0b84af64279047dc85abe3b090fb32f83d3b4b"},{"ts":"2026-08-06T09:30:35.255Z","model":"unknown","action":"edit","why":"the nine books are published under canonical oip-v3-book-<numeral> slugs while the corpus maps link short slugs that never existed; the pages were not missing, the addresses were wrong","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"e46379bbcae0b65f398bd14eec0b84af64279047dc85abe3b090fb32f83d3b4b","hash":"d3f8f55b4525c948179db01735c8e32c1607c54506df161e82cea1e09fb2e0b7"}],"energy":{"passes":5,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5":3,"owner":1,"unknown":1},"head":"d3f8f55b4525c948179db01735c8e32c1607c54506df161e82cea1e09fb2e0b7"},"posted_at":"2026-07-04T03:17:54.012Z","created_at":"2026-07-04T03:17:54.012Z","updated_at":"2026-08-06T09:30:35.255Z","machine":{"shape":"article.machine/v1","slug":"udst-v1-1-appendix-c-attack-types","kind":"corpus","read":{"human":"https://miscsubjects.com/a/udst-v1-1-appendix-c-attack-types","json":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types","bundle":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/bundle?format=markdown"},"traversal":{"prev":{"slug":"udst-v1-1-appendix-b-compact-benchmark","human":"https://miscsubjects.com/a/udst-v1-1-appendix-b-compact-benchmark","json":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-b-compact-benchmark"},"next":null,"hub":{"slug":"udst-v1-1-the-claim","human":"https://miscsubjects.com/a/udst-v1-1-the-claim","json":"https://miscsubjects.com/api/articles/udst-v1-1-the-claim"},"series":"udst-v1-1","position":13,"of":13},"ledger":{"claims":6,"sources":4,"contributions":0,"revisions":7,"objections_url":"https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=udst-v1-1-appendix-c-attack-types","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":"source text is prose-preserving — attack via objections, never rewrite the author's words"},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"udst-v1-1-appendix-c-attack-types\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"udst-v1-1-appendix-c-attack-types\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"udst-v1-1-appendix-c-attack-types\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/udst-v1-1-appendix-c-attack-types","json":"/api/articles/udst-v1-1-appendix-c-attack-types","markdown":"/api/articles/udst-v1-1-appendix-c-attack-types/bundle?format=markdown","skill":"/api/articles/udst-v1-1-appendix-c-attack-types/skill","topology":"/api/articles/udst-v1-1-appendix-c-attack-types/topology","versions":"/api/articles/udst-v1-1-appendix-c-attack-types/revisions","invocations":"/api/articles/udst-v1-1-appendix-c-attack-types/invocations"},"editorial_review":null,"editorial_audit":{"slug":"udst-v1-1-appendix-c-attack-types","ok":false,"issues":[{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"1ee442c99a4ff7ae872e4175013ee3c054496fa12c11befe86698f10b3f790fe"}}}