miscsubjectsAI governance
Object Invocation Protocol · protocol specification

APPENDIX C — Attack Types

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification · traversal JSON in-band
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-appendix-c-attack-types
**This page as JSON:** https://miscsubjects.com/api/articles/oip-appendix-c-attack-types
**Machine bundle:** https://miscsubjects.com/api/articles/oip-appendix-c-attack-types/bundle?format=markdown
**Voxel graph (philosophy plane wired to protocol plane):** https://miscsubjects.com/api/articles/oip/voxels
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.
  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

Key evidence

0 claims · tier-ranked · API
Model review1 contributions · 1 modelExpand the recursive review layer
1 / 1
grok/grok-4.3atomizer
atomize2026-07-07 08:37
atomize · 13 claims
inspect — what it was prompted & output
prompted with
You are the claim atomizer for the miscsubjects.com philosophy and OIP corpus. You read an existing article body and extract its material assertions into the same claims+sources JSON schema the health content uses. The body is read-only input.

ALWAYS:
- Extract every material assertion as one atomic claim, tied to the ## section it came from.
- Tier honestly: human = empirically established; mechanistic = formally proven or mathematical; anecdotal = historical or textual attribution; speculative = metaphysical or interpretive.
- Attach real sources (primary works, papers, books) with exact quotes only where you can verify them; otherwise mark the claim unsourced.
- Prefer fewer, harder claims over many soft ones.

NEVER:
- Never rewrite, summarize, or output the body.
- Never invent a URL, quote, or publication.
- Never duplicate an existing claim text.

input: atomize oip-appendix-c-attack-types
it output
{
  "claims": [
    {
      "id": "c1",
      "text": "Attack type Definition occurs when terms are incoherent.",
      "section": "# APPENDIX C — Attack Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Defines one of eight attack types used to evaluate claims in the OIP corpus."
    },
    {
      "id": "c2",
      "text": "Attack type Logic occurs when conclusion does not follow.",
      "section": "# APPENDIX C — Attack Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Defines one of eight attack types used to evaluate claims in the OIP corpus."
    },
    {
      "id": "c3",
      "text": "Attack type Empirical occurs when a real case falsifies.",
      "section": "# APPENDIX C — Attack Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Defines one of eight attack types used to evaluate claims in the OIP corpus."
    },
    {
      "id": "c4",
      "text": "Attack type Scope occurs when full-scope accounting is impossible or misused.",
      "section": "# APPENDIX C — Attack Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Defines one of eight attack types used to evaluate claims in the OIP corpus
2d753db350d0966f
Machine verification: /api/articles/oip-appendix-c-attack-types/contributions
oip-appendix-c-attack-types · posted 2026-07-04 · updated 2026-07-17 · 2 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 5 model passes · 5007 tokens · $0 · 4 models
chain head d9557f64e1ba31dd
edit claude-fable-5 · 2026-07-04 04:33 · tokens unrecorded · c8edb0cc2e36
edit claude-fable-5 · 2026-07-04 05:01 · tokens unrecorded · 4135395105be
atomize grok/grok-4.3 · 2026-07-07 08:37 · 5007 tok · ba31d768ac44
score scorer · 2026-07-07 08:37 · tokens unrecorded · 0a87ee262b6f
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · d9557f64e1ba
verify chain →
Live ledger · 41 payloads · 0 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 04:46
JCI_CLASSIFY jci · HTTP 200 · 2026-07-29 03:56
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 03:56
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 03:11
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 03:11
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 03:09
view full ledger & cards →
OIP REST + ledger
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}