## §SELF — miscsubjects (paste without context)

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `udst-v1-1-appendix-c-attack-types`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Paste entire block into Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Paste this entire block into Grok, GPT, or Gemini. They can READ the ledger below and RETURN evidence via ingest (see § LLM manifest).

## Article
- **slug:** `udst-v1-1-appendix-c-attack-types`
- **title:** UDST: V1 1 Appendix C Attack Types
- **url:** https://miscsubjects.com/a/udst-v1-1-appendix-c-attack-types
- **register:** oip_protocol
- **updated:** 2026-07-04T05:03:15.628Z
- **tags:** OIP, UDST, systems-theory, deterministic

## Body

# Appendix 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 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.

2. **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.

3. **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.

4. **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.

5. **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.

6. **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.

7. **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.

8. **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.

A 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.


---

## Corpus map
- Previous: [UDST: V1 1 Appendix B Compact Benchmark](/a/udst-v1-1-appendix-b-compact-benchmark)
- Series start: [UDST v1.1 — The Claim](/a/udst-v1-1-the-claim)
- Kin: [Book V — The Machine Plane](/a/oip-machine-plane) · [Total Structure](/a/oip-total-structure)

## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (3 model passes)
- chain valid: yes · head: `feb76dfc01da4bc3`

- fill · claude-fable-5 · 2026-07-04T03:40 · hash `0b06640a9912`
- edit · claude-fable-5 · 2026-07-04T04:39 · hash `4275adf4de1b`
- edit · claude-fable-5 · 2026-07-04T05:03 · hash `feb76dfc01da`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"udst-v1-1-appendix-c-attack-types","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest udst-v1-1-appendix-c-attack-types|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim udst-v1-1-appendix-c-attack-types|tier|assertion`
- **iMessage ask:** `udst-v1-1-appendix-c-attack-types|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects (paste without context)

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `udst-v1-1-appendix-c-attack-types`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-c-attack-types/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*