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

## Body

# BOOK II — OBLIGATION

## Capability Creates Debt

Obligation scales with capability. The greater the capacity, the greater the violation in withholding remedy. Hierarchy creates obligation downward, not privilege upward. The capable are not owed deference for their capability; they are **indebted by it** — to those who cannot remedy, and to the systems that depend on actors of strength to check and correct them. The self is a system and is not exempt: the standard applied outward applies inward without exception.

Three qualifiers keep the debt rigorous rather than sentimental:

**Effective, not abstract.** Capability means effective remedy-capacity: capability × proximity × leverage. Abstract power without proximity or leverage is not capability for this purpose.

**Bounded, not infinite.** The obligation is limited by capability, proximity, leverage, and actual remedy. The structure requires no infinite sacrifice.

**Triggered, not standing.** The obligation activates only when the harmed cannot self-remedy or remedy through the system. Voluntary inaction by the harmed does not invoke it.

*Observed instance (Book VI):* the build's capability tokens are this clause compiled. A delegation is scoped to named objects, expiring on a TTL, capped in uses, ceilinged in risk, pinnable in arguments, revocable instantly, and ledgered on every attempt — bounded, triggered, effective, in code. When Book II says obligation is bounded, it now points at a running implementation of what "bounded" means.

## The Measure

Moral strength is not intention and not sentiment. It is the deployment of capability toward relief of remediable harm — and the cost endured to hold the line on behalf of those who stand behind it. The measure of a person or a system: **what will they endure on behalf of those who cannot remedy for themselves.** Not what they declare; not what they intend; what they hold, under pressure, when holding costs something. The line is only a line if it does not move when tested. Strength is measured at the point of cost — and under A₁₁, the point of cost is where the receipts are.

## The Disclosure Doctrine

When a capable actor discovers a finding, method, or technology whose benefit is **moral in kind** — remediating conditions for those who cannot remediate for themselves — the following governs its handling:

**D1 — Anti-enclosure.** A benefit of great moral use must not be privatized against those who cannot pay for access. To deny people remedy for reasons of economics, heredity, position, or circumstance is a wrong under A₄: it converts a curable condition into tolerated remediable subjugation, with the discoverer as the capable actor who withheld.

**D2 — Disclosure as invariant installation.** Public disclosure of a novel method is invariant installation applied to the knowledge commons itself: a published method cannot afterward be enclosed by another party. One publication event permanently closes the enclosure pathway for everyone downstream — least action at the level of the commons. Defensive publication is the fulcrum move of the knowledge domain.

**D3 — The shield, never the sword.** Where a grace period exists between disclosure and claimability, the window may be used only to *prevent* enclosure by extractive parties — never to execute enclosure oneself. A claim filed under D3 must terminate in open license. Any other use is predation wearing the doctrine's clothing.

**D4 — The humility clauses.** Every disclosure carries three declarations, in order: novelty is queried, not claimed ("is any of this new?" precedes "this is new" — and if nothing is new, the correct response is gratitude for the review); utility is offered, not imposed, with intended deployment and limits stated; falsification is invited, with the kill conditions named per Book X.

**D5 — Expedition.** When remediation of a standing wrong becomes available, delay is a cost borne by the affected who cannot self-remedy. Expedition is a term of the debt, not a courtesy. Nothing violates a person more than to suffer a condition they cannot resolve; the discoverer who sits on the resolution converts their capability directly into the fourth condition of injustice.

**D6 — The drop.** *New in v3.0; generalized from the build's Tap & Go primitive.* **A disclosure is complete only when it is operable by a zero-context recipient.** Publication that requires the reader to assemble scattered pieces — the method here, the credentials there, the proof rule somewhere else, the tacit knowledge nowhere — has disclosed a description, not a capability. The build's form: one copied drop carrying credential, protocol, object map, search pattern, execute shape, and receipt rule together, such that a recipient with nothing but the drop can act and prove the action. The general form: disclose the way you would delegate — completely, executably, with the proof loop included. D6 is the operational test of D1 through D5: if the trapped cannot *run* the remedy from what you published, you have published marketing.

The doctrine is self-interested correctly understood, like everything in the structure: the actor who opens the door they walked through lives afterward in a commons where doors open. But its floor is not the incentive. Its floor is A₄.

## The Remedy Hierarchy

When obligation triggers, the superior remedy is **invariant installation** over acute relief. Charity treats the sample; the invariant changes the distribution. A capable actor who answers systemic harm with one-off relief has measured wrong — not acted wrongly, measured wrongly. Acute remedy is indicated only where the harm is genuinely singular or the invariant unreachable from the actor's position. Both modes exist; the structural mode dominates wherever it is reachable.

---

# PLANE TWO — THE WAY

---

## 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-ii-obligation/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: `e77a8a79d138425b`

- edit · claude-fable-5 · 2026-07-04T04:34 · hash `c7f9ea8e467c`
- edit · claude-fable-5 · 2026-07-04T05:02 · hash `e77a8a79d138`

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