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

## Body

## Claim

Raw source material lives outside the repo and outside any single prompt. Normandy pages point to source lineage, bundles, routes, and ledgers rather than duplicating raw sprawl. The source universe is the collection of all original documents, data, and records that exist independently of the page. Normandy pages reference those objects through URLs, receipts, and bundle routes. They do not copy the full content into the page body.

## Object shape

The Normandy page is a linked article object. It contains a readable body, claim atoms, source lineage, provenance, reviews, bundle route, and traversal metadata. The body states one operational point. Claim atoms are single assertions. Source lineage lists the external URLs that hold the original material. Provenance records how the page was built. Reviews record acceptance or rejection. The bundle route returns the page plus its claims and sources in one payload. Traversal metadata records the links to other pages.

## Source lineage

Source material for this page is stored at the following routes:

- https://miscsubjects.com/a/normandy supplies the definition of Normandy as the landing surface that converts source material into linked article objects.
- https://miscsubjects.com/a/oip supplies the definition of Object Invocation Protocol and the loop of object, invoke, ledger, receipt, replay, repair.
- https://miscsubjects.com/api/articles/constitution supplies the constitutional rules that govern article construction.
- https://miscsubjects.com/api/protocol/thread-update supplies the mechanism that appends updates to the ledger.
- https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown supplies the full OIP structure in bundle form.

Each URL is an independent object. The Normandy page records these URLs in its source lineage section and does not embed their full content.

## What would break this

The page breaks if a source URL returns a different object than the one listed. The page breaks if the bundle route at /api/articles/oip-total-structure/bundle returns a format other than the declared markdown bundle. The page breaks if the ledger at /api/protocol/thread-update no longer records the invocation receipt for this page. The page breaks if any listed claim atom changes its text without a corresponding ledger entry.

## OIP implication

OIP treats the Normandy page as an invocable object. POST /api/dispatch with the page slug invokes the object. The invocation appends an entry to the ledger. The ledger returns a receipt at /api/dispatch?receipt=inv_ID. Subsequent GET requests to the same route replay the receipt. Any repair to the page creates a new invocation and a new receipt. The source URLs remain external; only the pointer and the receipt live inside the OIP loop.

## Next link

The next link is the bundle route for the OIP total structure: https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown. That route returns the complete OIP specification in one payload and serves as the immediate traversal target after this page.

## Claims (5)

- **c1** [human w=0.8] Raw source material exists outside the repository and outside any single prompt.
  - who_claims: grok/grok-4.3
  - sources: s1
- **c2** [human w=0.8] Normandy pages contain readable body, claim atoms, source lineage, provenance, reviews, bundle route, and traversal metadata.
  - who_claims: grok/grok-4.3
  - sources: s1
- **c3** [human w=0.8] Source URLs listed in this page are independent objects that remain outside the OIP loop.
  - who_claims: grok/grok-4.3
  - sources: s2, s3, s4, s5
- **c4** [human w=0.8] The page breaks when any listed source URL returns a different object or when the ledger no longer records the invocation receipt.
  - who_claims: grok/grok-4.3
  - sources: s2
- **c5** [human w=0.8] OIP invocation of the Normandy page appends to the ledger and returns a receipt at /api/dispatch?receipt=inv_ID.
  - who_claims: grok/grok-4.3
  - sources: s2

## Voxel graph (5 atoms · 13 edges)
- full graph: https://miscsubjects.com/api/articles/normandy-source-universe/voxels

## Article constitution

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

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

### s1 · other · ok
- title: Normandy definition
- url: https://miscsubjects.com/a/normandy
- summary: Defines Normandy as the landing surface that converts source material into linked article objects.
- claim_ids: c1, c2
- hash: `064252c2987ffbc8`

### s2 · other · ok
- title: Object Invocation Protocol
- url: https://miscsubjects.com/a/oip
- summary: Defines OIP, the invocation loop, and the dispatch routes.
- claim_ids: c3, c4, c5
- hash: `5c06153c50a5ed69`

### s3 · other · ok
- title: Article constitution
- url: https://miscsubjects.com/api/articles/constitution
- summary: Supplies constitutional rules that govern article construction.
- claim_ids: c3
- hash: `ebef905fcbee8362`

### s4 · other · ok
- title: Thread update protocol
- url: https://miscsubjects.com/api/protocol/thread-update
- summary: Mechanism that appends updates to the ledger.
- claim_ids: c3
- hash: `b29f9e64c2b3ccd3`

### s5 · other · ok
- title: OIP total structure bundle
- url: https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown
- summary: Returns the complete OIP specification in bundle form.
- claim_ids: c3
- hash: `2dd0fc5bd85fcd8a`

## Provenance (2 model passes)
- chain valid: yes · head: `78c7d8ab7c297313`

- write · grok/grok-4.3 · 2026-07-04T20:33 · hash `d1cc33fa3a7b`
- wire-normandy-shelf · codex · 2026-07-04T20:33 · hash `78c7d8ab7c29`

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