miscsubjects.com
Evidence review · oip_protocol

UDST: V1 1 Capability And Obligation

#OIP#UDST#systems-theory#deterministic
bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `udst-v1-1-capability-and-obligation`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/udst-v1-1-capability-and-obligation

### 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)
- **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
- **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
- **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

### 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.*

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

udst-v1-1-capability-and-obligation · condition map

Evidence map

Hover a node — its path lights up. Click to open the article.

Full map →
Talk to this article
Tap a phone. Ask anything about UDST: V1 1 Capability And Obligation. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.

Related articles

udst-v1-1-capability-and-obligation · condition map

Open evidence map →
Oipprotocol rootoipPhilosophy Protocolfoundation protocolphilosophy-protocolPhilosophy Source Documentationsource corpusphilosophy-source-documentationOIP specificationnormative specoip-specOIP operating modeloperating loopoip-operating-modelTap & Goscoped dropoip-tap-goMachine-native JSONmachine payloadoip-machine-jsonOip Ledger Receiptsproof and receiptsoip-ledger-receiptsModels reviewing OIP articlesrecursive reviewoip-model-review-loopOip Curlterminal operationoip-curl
Ask this article · 2 suggested prompts
topology · JSON · question graph

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

For my medical situation, what can you answer from your catalogue about UDST: V1 1 Capability And Obligation — and what would you need me to tell you first?
ask udst-v1-1-capability-and-obligation condition gaps · paste includes §SELF
What good and bad outcomes are documented for UDST: V1 1 Capability And Obligation (studies vs anecdotes)?
ask udst-v1-1-capability-and-obligation good bad experiences · paste includes §SELF
Add your experience or question
Think this article is wrong?
Call bullshit on CharlieOS →
Loading more articles…