## §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:** `normandy-claim-voxel`
- **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/normandy-claim-voxel/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/normandy-claim-voxel/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/normandy-claim-voxel/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/normandy-claim-voxel/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/normandy-claim-voxel/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/normandy-claim-voxel/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:** `normandy-claim-voxel`
- **title:** Normandy: A Claim Is A Traversal Unit
- **url:** https://miscsubjects.com/a/normandy-claim-voxel
- **register:** source_ledger
- **updated:** 2026-07-04T20:38:35.532Z
- **tags:** normandy, convergence, oip, machine-traversal

## Body

## Claim
A claim voxel is the atomic machine-readable unit that Normandy uses to store one assertion. The voxel carries an identifier, a tier label, a slot that records where the assertion sits inside the article, a list of source identifiers, an evidence basis descriptor, a materiality flag that marks whether the assertion changes action or understanding, a posted_by field, a falsifier that states the exact condition under which the assertion is withdrawn, and adjacent link references that point to the next claim voxels required for traversal.

## Object shape
The object shape of a claim voxel is a JSON fragment with fixed keys: id, text, section, tier, source_ids, evidence_basis, materiality, posted_by, falsifier, and adjacent_links. The id is a string unique inside the article ledger. The text field holds one assertion written as a single declarative sentence. The section field records the heading under which the assertion appears. The tier field accepts one of human, preclinical, anecdotal, mechanistic, or speculative. The source_ids array lists the identifiers of source objects that back the assertion. The evidence_basis field states whether the assertion rests on primary data, secondary synthesis, or direct observation. The materiality flag is a boolean that is true when the assertion alters a downstream decision or model state. The posted_by field records the ledger entry that introduced the voxel. The falsifier field is a short conditional statement that defines the observation or measurement that would render the assertion false. The adjacent_links array contains the ids of other claim voxels that must be read next to complete the traversal path.

## Source lineage
Source lineage for claim voxels is recorded through the source_ids array that points to objects stored at /api/articles. Each source object contains its own id, type, url, title, and summary. The lineage chain is traversed by following the source_ids from the voxel into the source object, then from the source object into any parent source objects listed in its own lineage field. The route /api/articles returns the current state of every source object referenced by voxels inside an article. The route /a/normandy shows the article that first defined the Normandy landing surface and the claim voxel structure. The route /a/oip shows the protocol specification that defines how objects are invoked and how receipts are issued. The route /api/articles/constitution returns the ledger constitution that governs claim registration and falsifier enforcement. The route /api/protocol/thread-update returns the endpoint used to append new claim voxels to an existing article ledger.

## What would break this
The claim voxel structure breaks when any required key is missing from the JSON fragment, when the tier label does not match one of the five allowed values, when the falsifier field is empty or cannot be evaluated against observable data, when a source_id references a non-existent source object, or when the adjacent_links array creates a cycle that prevents linear traversal. The structure also breaks when the materiality flag is set to true but no downstream object or decision depends on the assertion. In each case the receipt returned by POST /api/dispatch contains an error code and the ledger entry is rejected.

## OIP implication
Under OIP the claim voxel is the work object. Invocation occurs when a client posts the voxel JSON to POST /api/dispatch with the key set to the article slug. The ledger appends the voxel, assigns an invocation identifier, and returns a receipt at /api/dispatch?receipt=inv_ID. The receipt proves that the voxel was accepted, that its falsifier was recorded, and that its adjacent_links were validated against existing voxels. Subsequent GET /api/dispatch?invoke=KEY&body=... calls retrieve the current state of the voxel and any updated source_ids. Repair occurs when a new voxel arrives that matches the falsifier condition of an earlier voxel; the ledger marks the earlier voxel superseded and issues a new receipt. Replay occurs when a client requests the full chain of voxels for a given article slug and receives the ordered list with their receipts.

## Next link
The next link after normandy-claim-voxel is the article at /a/oip that specifies the full Object Invocation Protocol including dispatch routes, receipt format, and ledger conformance rules.

## Claims (5)

- **c1** [human w=0.8] A claim voxel stores one assertion together with tier, source_ids, evidence_basis, materiality, posted_by, falsifier, and adjacent_links.
  - who_claims: grok/grok-4.3
  - sources: s1
- **c2** [human w=0.8] The object shape of a claim voxel is a JSON fragment containing exactly the keys id, text, section, tier, source_ids, evidence_basis, materiality, posted_by, falsifier, and adjacent_links.
  - who_claims: grok/grok-4.3
  - sources: s2
- **c3** [human w=0.8] Source lineage is followed by resolving each source_id in a voxel to the corresponding source object stored at /api/articles.
  - who_claims: grok/grok-4.3
  - sources: s3
- **c4** [human w=0.8] A claim voxel is rejected by the ledger when a required key is missing, when the tier is invalid, when the falsifier is empty, or when adjacent_links form a cycle.
  - who_claims: grok/grok-4.3
  - sources: s4
- **c5** [human w=0.8] Under OIP a claim voxel is invoked by POST /api/dispatch, appended to the ledger, and confirmed by a receipt that can be retrieved at /api/dispatch?receipt=inv_ID.
  - who_claims: grok/grok-4.3
  - sources: s5

## Voxel graph (5 atoms · 10 edges)
- full graph: https://miscsubjects.com/api/articles/normandy-claim-voxel/voxels

## Article constitution

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

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

### s1 · other · ok
- title: Normandy landing surface definition
- url: https://miscsubjects.com/a/normandy
- summary: Defines the Normandy article structure that uses claim voxels as atomic units.
- claim_ids: c1
- hash: `7817337488a0e8cf`

### s2 · other · ok
- title: Object Invocation Protocol specification
- url: https://miscsubjects.com/a/oip
- summary: Specifies the JSON shape and dispatch mechanics for work objects including claim voxels.
- claim_ids: c2
- hash: `d0ab1338ee6eb008`

### s3 · other · ok
- title: Ledger constitution for claim registration
- url: https://miscsubjects.com/api/articles/constitution
- summary: States the rules for source lineage and source object resolution.
- claim_ids: c3
- hash: `fb72d27948dce5ff`

### s4 · other · ok
- title: Thread update protocol for ledger appends
- url: https://miscsubjects.com/api/protocol/thread-update
- summary: Defines the validation checks that cause a claim voxel to be rejected.
- claim_ids: c4
- hash: `3033da1e943b12b6`

### s5 · other · ok
- title: OIP total structure bundle
- url: https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown
- summary: Documents the full OIP loop and receipt format used for claim voxel invocation.
- claim_ids: c5
- hash: `72eabbcde2812167`

## Provenance (2 model passes)
- chain valid: yes · head: `968b7531bc64a028`

- write · grok/grok-4.3 · 2026-07-04T20:33 · hash `c5c4bba48c24`
- wire-normandy-shelf · codex · 2026-07-04T20:33 · hash `968b7531bc64`

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