Evidence review · oip_protocol

Unified Philosophy: Capability Weighted Obligation

#OIP#unified-philosophy#ethics#systems

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:** `unified-philosophy-capability-weighted-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/unified-philosophy-capability-weighted-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/unified-philosophy-capability-weighted-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/unified-philosophy-capability-weighted-obligation/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/unified-philosophy-capability-weighted-obligation/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/unified-philosophy-capability-weighted-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-Weighted Obligation

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.

This applies to the self as a system equally as to systems of systems. The self is not exempt. The same standard applied outward applies inward without exception.

---

Claims

Claim: Obligation scales with capability · Tier: system · Confidence: high
Claim: Hierarchy creates obligation downward, not privilege upward · Tier: system · Confidence: high
Claim: The self is subject to the same standard as external systems · Tier: system · Confidence: high

Example

A senior engineer discovers a safety flaw in their product. They have the unique capability to understand and fix it. Withholding the fix is a greater violation than if a junior engineer (who lacks the capability to fix it) had merely noticed the symptom. The obligation is proportional to the capability.

What Would Falsify This

Evidence that flat obligation (equal regardless of capability) produces better outcomes.
Cases where deference to capability consistently produced superior systemic results than obligation downward.

---

Corpus map

Previous: Unified Philosophy: Moral Strength And The Lines
Next: Unified Philosophy: How Systems Ought Check One Another
Series start: The Situation Report
Kin: Total Structure root · GRAIN

Talk to this article

Tap a phone. Ask anything about Unified Philosophy: Capability Weighted 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.

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 Unified Philosophy: Capability Weighted Obligation — and what would you need me to tell you first?

ask unified-philosophy-capability-weighted-obligation condition gaps · paste includes §SELF

What good and bad outcomes are documented for Unified Philosophy: Capability Weighted Obligation (studies vs anecdotes)?

ask unified-philosophy-capability-weighted-obligation good bad experiences · paste includes §SELF

Capability-Weighted Obligation

Claims

Example

What Would Falsify This

Related

Corpus map

Evidence map

Related articles