## §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:** `oip-v3-book-ix-the-amendment-protocol`
- **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/oip-v3-book-ix-the-amendment-protocol/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-v3-book-ix-the-amendment-protocol/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-v3-book-ix-the-amendment-protocol/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/oip-v3-book-ix-the-amendment-protocol/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/oip-v3-book-ix-the-amendment-protocol/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-v3-book-ix-the-amendment-protocol/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:** `oip-v3-book-ix-the-amendment-protocol`
- **title:** Total Structure v3: Book IX — THE AMENDMENT PROTOCOL
- **url:** https://miscsubjects.com/a/oip-v3-book-ix-the-amendment-protocol
- **register:** oip_protocol
- **updated:** 2026-07-04T05:02:48.621Z
- **tags:** philosophy, oip, book, total-structure, systems-theory

## Body

# BOOK IX — THE AMENDMENT PROTOCOL

*New in v3.0. A₁₂ requires that the structure revise itself; A₁₂ equally requires that it never revise silently. This book is the governance of the document you are reading — the self-altering mechanism, chained.*

## The Document Is an Object

This document is an object under its own grammar (Book VI): it has a contract (this book), a proof path (its version ledger), tests (Book X's surfaces), and a repair loop (the amendment classes below). Accordingly:

**IX.1 — Append-only versioning.** No version of this document is ever destroyed or edited in place. Every amendment produces a new version with lineage to its predecessor. A silent edit is a forged receipt, and a forged receipt anywhere voids trust everywhere.

**IX.2 — Mandatory changelog.** Every version ships its changelog — every non-trivial editorial decision declared, with rationale. A document about auditable systems that cannot itself be audited is a one-way mirror.

**IX.3 — Typed claims.** Every claim in the document carries one of four types — *axiom*, *derivation*, *observed*, *open* — and every *observed* claim carries a freshness window. This typing is what makes amendment tractable: you cannot correctly revise what you have not correctly typed.

## The Amendment Classes

Every proposed change is one of four classes, each with its own bar:

**Class P — Patch.** Compression, clarity, cross-reference, typo. The semantic diff must be empty: a patch that changes what the document claims is a misfiled revision and is rejected as a patch. Bar: the compression axiom — fewer moves, same load.

**Class R — Revision.** Changes a *derivation* or *observed* claim. Bar: an attack per Book X's protocol that survived — exact claim named, surface named, type classified, full-scope accounting shown, minimum patch proposed. The revision *is* the minimum patch of a surviving attack. No surviving attack, no revision: the document does not change to taste.

**Class E — Extension.** Adds structure — a book, a doctrine, an axiom. Bar, threefold: the addition must ship its own falsification conditions (an unfalsifiable extension is decoration); it must pass the **anti-bloat rule** — added load must exceed added length, accounted in the changelog (this is how "make it longer" and "keep it compressed" reconcile: length is permitted exactly where it carries proportional load); and if the extension is an axiom, it must survive A₀ — published with its negation and the reason the negation collapses.

**Class X — Reversal.** Removes or inverts an axiom. Bar: the full attack protocol at the axiom's dependency depth, plus explicit accounting of everything downstream that falls with it (per Appendix A's map). And one exclusion, absolute: **A₄ is not amendable.** A structure that can amend its own moral floor under pressure has no floor — it has a price. The kill switch is the one place where self-alteration is prohibited *by the self-alteration protocol itself*, and the prohibition is the protocol's proof of seriousness: a document that reserves nothing reveres nothing. If A₄ falls, the document does not get revised. It gets refuted, and its refutation should be published with the same lineage discipline as its versions.

## The Review Recursion

Modeled on the running loop of Book VI, installed here:

**IX.4 — Zero-context review.** On a declared cadence, the document is submitted to zero-context readers — human or model — who score it on two separate axes: clarity (can a cold reader operate the structure from the text alone?) and conformance (does the document obey its own rules — typed claims, fresh windows, declared nodes, compressed prose?). Scores and named gaps are ledgered.

**IX.5 — Failing review queues revision.** A score below the declared threshold queues a Class P or Class R amendment targeting the named deficiency. A gap named by a reviewer — a concept the document needs and lacks — queues a Class E extension, which then enters the same review cycle. The document grows where its readers demonstrate its absence, not where its author enjoys its presence.

**IX.6 — Freshness enforcement.** Every *observed* claim is re-verified within its freshness window. A stale *observed* claim is automatically demoted to *open* — not deleted, demoted — until re-verified. The existence proof of Book VI is the first client of this rule: its claims about the running build expire and must be re-receipted, because a philosophy citing a dead build as live evidence is exactly the declared-success-without-receipts that Book III calls capture.

**IX.7 — The objection ledger is live.** Settled objections (Book IV) are carried in the document with their answers. An entry is settled only while its answer survives; any attacker may reopen an entry by showing the answer stale or the design changed. A ledger that cannot be reopened is dogma in rigor's costume.

## The Capture Guard

The amendment protocol is itself a system, and systems get captured. Three guards:

**IX.8 — Amendment by protocol, not by position.** No steward, including the original author, may amend outside the classes and bars above. The author's advantage is proximity, not privilege: their amendments face the same protocol.

**IX.9 — The fork rule.** If a steward refuses the minimum patch of a surviving attack, the correct move is not surrender and not sabotage — it is **fork with declared lineage**: a new version line, publicly derived, carrying the surviving patch, with the refusal documented in its changelog. The protocol can be routed around, but only in the open. A secret fork is a capture; a declared fork is a check. This rule is Book III's checking network applied to the document itself: no single steward, including the maker, is the load-bearing structure — the lineage discipline is.

**IX.10 — Recursion audit.** The review loop itself is reviewable: its cadence, thresholds, and reviewer selection are declared, ledgered, and amendable under Class R. A self-review loop whose parameters are hidden is a one-way mirror at the meta-level — and surface S8 (Book X) is the standing invitation to attack it.

This book is the difference between a philosophy and a living protocol. v1 declared. v2 organized and armed. v3 breathes on a ledger: strained by cold readers, fractured on schedule, repaired with lineage, forkable in the open, and reserved in exactly one place — the floor.

---

---

## Corpus map
- Canonical shelf: [Total Structure root](/a/oip-total-structure)

## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/oip-v3-book-ix-the-amendment-protocol/voxels

## Article constitution

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

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

## Provenance (2 model passes)
- chain valid: yes · head: `9ce3c158d259c75a`

- edit · claude-fable-5 · 2026-07-04T04:34 · hash `0740d393363d`
- edit · claude-fable-5 · 2026-07-04T05:02 · hash `9ce3c158d259`

## 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-v3-book-ix-the-amendment-protocol/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-v3-book-ix-the-amendment-protocol/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"oip-v3-book-ix-the-amendment-protocol","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest oip-v3-book-ix-the-amendment-protocol|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim oip-v3-book-ix-the-amendment-protocol|tier|assertion`
- **iMessage ask:** `oip-v3-book-ix-the-amendment-protocol|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:** `oip-v3-book-ix-the-amendment-protocol`
- **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-v3-book-ix-the-amendment-protocol/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/oip-v3-book-ix-the-amendment-protocol/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.*