## §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-capability-and-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/udst-v1-1-capability-and-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/udst-v1-1-capability-and-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/udst-v1-1-capability-and-obligation/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/udst-v1-1-capability-and-obligation/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/udst-v1-1-capability-and-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/udst-v1-1-capability-and-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:** `udst-v1-1-capability-and-obligation`
- **title:** UDST: V1 1 Capability And Obligation
- **url:** https://miscsubjects.com/a/udst-v1-1-capability-and-obligation
- **register:** oip_protocol
- **updated:** 2026-07-04T05:03:16.622Z
- **tags:** OIP, UDST, systems-theory, deterministic

## Body

# Capability and Obligation

If injustice is systems-level entropy and the architecture favors negentropy, then the actors who can reduce systems-level entropy are obligated to reduce it.

Capability creates bounded obligation. Three qualifiers.

**Capability** means effective remedy-capacity — capability multiplied by proximity multiplied by leverage. Abstract power without proximity or leverage is not capability for this purpose. In the build, capability is a directory row: a named, typed, scoped operation with a defined contract and a working example. `GET /api/dispatch?key=NOW` returns the NOW row, which includes its contract, its arguments, and its example invocation. A row without a working example is abstract power without leverage; it is not capability. The directory contains 731 rows, and each one that has been proven by a live receipt is capability. The rest are aspirational.

**Bounded** means the obligation is limited by capability, proximity, leverage, and actual remedy. The framework requires no infinite sacrifice. In the build, boundedness is the capability token: a scoped, time-limited, use-limited credential that grants exactly the access needed and no more. A `row:NOW` token can fire NOW but cannot touch LOCAL_EXEC. An `act` token can fire any capability but is gated by risk_ceiling and owner_gate. The obligation is bounded by the token's scope, not by the actor's good intentions.

**Triggered** means the obligation activates only when the harmed actor cannot self-remedy or remedy through the system. Voluntary inaction by the harmed does not invoke it. In the build, this is the `?ask` endpoint: a model that does not know how to act can ask the system, and the system returns the exact capability with a run-now URL. If the model can self-remedy by reading the directory, it should. If it cannot, the system is obligated to provide the remedy. But the system is not obligated to act on behalf of a model that refuses to read the map.

The remedy method is the load-bearing prescription.

The superior remedy is invariant installation. Most personal injury is a sample in a systemic distribution. The correct move is not to soothe the sample. It is to trace the harm to its systemic intersection of highest occurrence and install the minimum structural change that closes the predation pathway for everyone downstream.

This is least action applied to remedy. The criterion is not maximum effort. It is maximum leverage with minimum moves. One correctly placed invariant can extinguish multiple predation pathways across adjacent systems. In the build, this is the migration: a single SQL migration that fixes a schema defect for all future invocations, not a one-off manual edit. The `write_law` migration (0204) added real examples to 699 rows, closing the "model cannot figure out how to act" predation pathway for every future model. One migration, one invariant, all downstream actors protected.

The framework distinguishes dysfunction from capture. A dysfunctional system is failing its charter and can be remedied through the system. A captured system is performing its charter for a different principal than the one it declared; the flags still fly, but the institution serves a buyer it does not name. In the build, this is the directory snapshot: a JSON file that mirrors the live directory rows, so any agent can read the declared contract and compare it to the actual implementation. If the snapshot says a row has an example but the live row does not, the system is dysfunctional and can be remedied by a migration. If the snapshot is deliberately not updated to hide a capture, the system is captured and the remedy is to expose the mismatch.

Compliance with functioning systems is the diagnostic instrument; it shows where and how a system fails. Compliance ends when the system breaks the actor, or breaks someone behind the actor who cannot remedy through it. From that point the obligation is not exit and not loyalty. It is invariant installation.


---

## Corpus map
- Previous: [UDST: V1 1 The Base Wrong](/a/udst-v1-1-the-base-wrong)
- Next: [UDST: V1 1 Logical Economics](/a/udst-v1-1-logical-economics)
- 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-capability-and-obligation/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: `dd9b8d09d45483b9`

- fill · claude-fable-5 · 2026-07-04T03:40 · hash `cde7cf92957d`
- edit · claude-fable-5 · 2026-07-04T04:39 · hash `fa2add6ef1c0`
- edit · claude-fable-5 · 2026-07-04T05:03 · hash `dd9b8d09d454`

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