## §SELF — miscsubjects portable reference

**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**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `udst-v1-1-appendix-a-compact-definitions`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/udst-v1-1-appendix-a-compact-definitions/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-appendix-a-compact-definitions/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-appendix-a-compact-definitions/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-a-compact-definitions/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-a-compact-definitions/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-appendix-a-compact-definitions/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

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `udst-v1-1-appendix-a-compact-definitions` v6 · content_hash `7749706d04d02852…` · thread_head genesis · 21 DIVs
- **thesis:** FLAGGED — this article's thesis does not reduce to one falsifiable root claim — audit finding, not fudged
  - undefined [?/active] 
  - undefined [?/active] 
  - undefined [?/active] 
  - undefined [?/active] 
  - undefined [?/active] 
  - undefined [?/active] 
  - undefined [?/active] 
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/udst-v1-1-appendix-a-compact-definitions/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/udst-v1-1-appendix-a-compact-definitions/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `udst-v1-1-appendix-a-compact-definitions`
- **title:** UDST: V1 1 Appendix A Compact Definitions
- **url:** https://miscsubjects.com/a/udst-v1-1-appendix-a-compact-definitions
- **register:** oip_protocol
- **updated:** 2026-07-17T02:37:50.760Z
- **tags:** OIP, UDST, systems-theory, deterministic

## Body

# Appendix A — Compact Definitions

**Full-scope system optimality** — durable agency, order, gain, auditability, and correct function under load, without contradiction, hidden cost, coercive maintenance, wasted energy, or tolerated remediable subjugation. In the build, this is the conformance suite: `GET /api/dispatch?conformance=1` verifies that all five properties hold on production.

**Full scope** — bounded by declared decision horizon, known and knowable affected parties, required accounting categories, and priced unresolved nodes. Costs that cannot be resolved are named, typed, bounded, and carried as uncertainty rather than excluded. In the build, this is the `?ask` endpoint: it returns the exact capability with scope, args, and example, so the decision horizon is declared, the affected parties are known, and the accounting categories are the capability's contract.

**Systems-level entropy** — a maintained lower-yield state requiring ongoing energy to suppress available higher-order function. In the build, this is the governor's recurrence class: a pattern of ledger events that repeats because the systemic cause has not been addressed. The energy required to suppress it is measured in operator attention and manual intervention.

**Injustice** — tolerated remediable subjugation: an actor beholden to a system, unable to remedy, where capable remedy exists in the same system, and the system tolerates non-remedy. In the build, this is a capability that exists but is not accessible to the actor who needs it: a row with no example, a token with the wrong scope, a migration that was applied but not documented. The actor is trapped by logic-cost, not material scarcity.

**Capability** — effective remedy-capacity (capability × proximity × leverage). In the build, this is a directory row: a named, typed, scoped operation with a working example and a live receipt. Abstract power without a working example is not capability.

**Obligation** — duty triggered by capability when the harmed actor cannot self-remedy or remedy through the system; bounded by capability, proximity, leverage, and actual remedy. In the build, this is the `?ask` endpoint: when a model cannot self-remedy by reading the directory, the system is obligated to provide the exact capability and run-now URL. The obligation is bounded by the token scope and the capability's contract.

**Invariant installation** — the minimum structural change that closes a recurrence pathway across a distribution. In the build, this is a migration: a single SQL change that fixes a schema or data defect for all future invocations, not a one-off manual edit. The 227 migrations are 227 installed invariants.

**Logical Unit** — the smallest auditable inference step, evaluable as true, false, unknown, conflicted, insufficient, or out of scope. In the build, this is a capability invocation: one `POST /api/dispatch` with one key, one body, and one receipt. The receipt is the auditable step.

**Surety** — Correctness × Auditability × Reproducibility × Adversarial Survival (multiplicative; any factor at zero collapses the score). In the build, this is the conformance score: `GET /api/dispatch?conformance=1` returns 15 clauses, each a factor in the surety score. If any clause fails, the surety for that dimension is zero.

**Logical Energy** — total physical and symbolic cost across the artifact's lifecycle. In the build, this is the sum of tokens, compute, latency, human review, and privacy risk for each invocation. The ledger records it per receipt.

**Logical Density (compressed)** — Surety / Logical Energy. In the build, this is the conformance score divided by the average invocation cost per capability.

**Task-Adjusted Logical Density (rigorous)** — Expected Verified Decision Value / Total Lifecycle Logical Cost, where Expected Verified Decision Value = Task Stakes × Correctness × Auditability × Reproducibility × Adversarial Survival × Actionability × Freshness, and Total Lifecycle Logical Cost = generation + retrieval + context + tool use + verification + red-team + repair + human review + privacy risk + failure risk + replay/adaptation cost + latency/opportunity cost. In the build, this is the router's election criteria: the router chooses the capability with the highest task-adjusted logical density for the given task, based on the task's stakes, deadline, privacy, budget, and required surety.

**Proof artifact** — replayable, ledgered output of a reasoning event, valid within declared scope, freshness window, and similarity class. In the build, this is the receipt: `GET /api/dispatch?receipt=INV_ID` replays the full invocation, including request, response, proof, and story. The receipt is valid only within the scope of the original capability, the freshness window of the token's TTL, and the similarity class of the task.

**Admission invariant** — context, tools, model outputs, router decisions, proof artifacts, and reuse events are untrusted until typed, scoped, provenance-bound, permissioned, adversarially checked, expiry-limited, and admitted into the proof graph. In the build, this is the capability gate: `capGateCheck` enforces type, scope, provenance, permission, expiry, and adversarial check before any invocation is admitted.

**Command plane** — the deterministic layer above stochastic weights that elects model, scaffold, context, tools, proof depth, red-team depth, privacy mode, and ledgering per task. In the build, this is the dispatch router: `POST /api/dispatch` does not invoke a model directly; it invokes a capability row, which is a deterministic contract. The router elects the model, scaffold, and context based on the capability's contract.

**Glass box** — a system whose external decisions, including the meta-decisions of the command plane, are typed, logged, replayable, challengeable, expiry-limited, and revocable. In the build, this is the receipt system: every invocation returns a receipt with `request_json`, `response_json`, `proof`, and `story`, all typed, logged, replayable, and challengeable. The meta-decisions (which model was elected, which context was admitted) are visible in the receipt.

**Structural isolation** — separation of raw-context ingestion, proof construction, verification, red-team, repair, and ledgering into distinct instances where risk requires. In the build, this is the role separation: the `sibling` worker ingests raw tasks, the `main` worker constructs proofs, and the `ledger` database stores the results. The instances are separated by worker type and database binding.


---

## Corpus map
- Previous: [UDST: V1 1 Attack Protocol](/a/udst-v1-1-attack-protocol)
- Next: [UDST: V1 1 Appendix B Compact Benchmark](/a/udst-v1-1-appendix-b-compact-benchmark)
- 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 (8)

- **undefined** [? w=?] 
- **undefined** [? w=?] 
- **undefined** [? w=?] 
- **undefined** [? w=?] 
- **undefined** [? w=?] 
- **undefined** [? w=?] 
- **undefined** [? w=?] 
- **undefined** [? w=?] 

## Voxel graph (8 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/udst-v1-1-appendix-a-compact-definitions/voxels

## Article constitution

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

## Source ledger (4)
- chain valid: no · head: ``

### build-migrations · doc
- title: Build Migration History
- url: https://miscsubjects.com/api/directory/migrations
- hash: ``

### dispatch-ask · api
- title: Dispatch Ask Endpoint
- url: https://miscsubjects.com/api/dispatch?ask=1
- hash: ``

### dispatch-conformance · api
- title: Dispatch Conformance Endpoint
- url: https://miscsubjects.com/api/dispatch?conformance=1
- hash: ``

### governor-recurrence · doc
- title: Governor Recurrence Classes
- url: https://miscsubjects.com/api/directory/governor
- hash: ``

## Provenance (4 model passes)
- chain valid: yes · head: `b17ad04c5ee3d7db`

- fill · claude-fable-5 · 2026-07-04T03:40 · hash `628c0db7e153`
- edit · claude-fable-5 · 2026-07-04T04:39 · hash `7c0d527d39b7`
- edit · claude-fable-5 · 2026-07-04T05:03 · hash `9eb08ae2e35a`
- voxel_divide · owner · 2026-07-17T02:37 · hash `b17ad04c5ee3`

## 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-appendix-a-compact-definitions/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-appendix-a-compact-definitions/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"udst-v1-1-appendix-a-compact-definitions","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest udst-v1-1-appendix-a-compact-definitions|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim udst-v1-1-appendix-a-compact-definitions|tier|assertion`
- **iMessage ask:** `udst-v1-1-appendix-a-compact-definitions|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**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-appendix-a-compact-definitions`
- **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-appendix-a-compact-definitions/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** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/udst-v1-1-appendix-a-compact-definitions/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

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*