## §SELF — miscsubjects portable reference

**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**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `oip-appendix-c-attack-types`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/oip-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/oip-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/oip-appendix-c-attack-types/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/oip-appendix-c-attack-types/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/oip-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/oip-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

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

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

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `oip-appendix-c-attack-types` v3 · content_hash `3a6fb92041f82fdb…` · thread_head genesis · 7 DIVs
- **thesis:** FLAGGED — this article's thesis does not reduce to one falsifiable root claim — audit finding, not fudged
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/oip-appendix-c-attack-types/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/oip-appendix-c-attack-types/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `oip-appendix-c-attack-types`
- **title:** APPENDIX C — Attack Types
- **url:** https://miscsubjects.com/a/oip-appendix-c-attack-types
- **register:** oip_protocol
- **updated:** 2026-07-17T02:36:01.969Z
- **tags:** philosophy, oip, appendix, systems-theory, total-structure

## Body

# APPENDIX C — Attack Types

1. **Definition** — terms are incoherent.
2. **Logic** — conclusion does not follow.
3. **Empirical** — a real case falsifies.
4. **Scope** — full-scope accounting is impossible or misused.
5. **Category-error** — a concept transferred across levels invalidly.
6. **Implementation** — the protocol cannot be executed.
7. **Prior-art** — the welded construction already exists.
8. **Falsifiability** — the counterexample condition cannot be met in practice.

A valid attack states its type, names its surface (S1–S8), names the exact claim, shows the work, and proposes the minimum patch. Surviving patches enter Law IX as Class R amendments.

---

---

## Corpus map
- Shelf root: [Total Structure v3 — root](/a/oip-total-structure)
- Kin appendices: [UDST Appendix B — Compact Benchmark](/a/udst-v1-1-appendix-b-compact-benchmark) · [UDST Appendix C — Attack Types](/a/udst-v1-1-appendix-c-attack-types)

## Claims (13)

- **c1** [speculative w=0.1] Attack type Definition occurs when terms are incoherent.
- **c2** [speculative w=0.1] Attack type Logic occurs when conclusion does not follow.
- **c3** [speculative w=0.1] Attack type Empirical occurs when a real case falsifies.
- **c4** [speculative w=0.1] Attack type Scope occurs when full-scope accounting is impossible or misused.
- **c5** [speculative w=0.1] Attack type Category-error occurs when a concept transferred across levels invalidly.
- **c6** [speculative w=0.1] Attack type Implementation occurs when the protocol cannot be executed.
- **c7** [speculative w=0.1] Attack type Prior-art occurs when the welded construction already exists.
- **c8** [speculative w=0.1] Attack type Falsifiability occurs when the counterexample condition cannot be met in practice.
- **c9** [speculative w=0.1] A valid attack states its type, names its surface (S1–S8), names the exact claim, shows the work, and proposes the minimum patch.
- **c10** [speculative w=0.1] Surviving patches enter Book IX as Class R amendments.
- **c11** [speculative w=0.1] Shelf root is Total Structure v3 at /a/oip-total-structure.
- **c12** [speculative w=0.1] Kin appendix UDST Appendix B is Compact Benchmark at /a/udst-v1-1-appendix-b-compact-benchmark.
- **c13** [speculative w=0.1] Kin appendix UDST Appendix C is Attack Types at /a/udst-v1-1-appendix-c-attack-types.

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

## Article constitution

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

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

## Provenance (5 model passes)
- chain valid: yes · head: `d9557f64e1ba31dd`

- edit · claude-fable-5 · 2026-07-04T04:33 · hash `c8edb0cc2e36`
- edit · claude-fable-5 · 2026-07-04T05:01 · hash `4135395105be`
- atomize · grok/grok-4.3 · 2026-07-07T08:37 · hash `ba31d768ac44`
- score · scorer · 2026-07-07T08:37 · hash `0a87ee262b6f`
- voxel_divide · owner · 2026-07-17T02:36 · hash `d9557f64e1ba`

## 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/oip-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/oip-appendix-c-attack-types/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"oip-appendix-c-attack-types","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest oip-appendix-c-attack-types|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim oip-appendix-c-attack-types|tier|assertion`
- **iMessage ask:** `oip-appendix-c-attack-types|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**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:** `oip-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/oip-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** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/oip-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

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

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