# Normandy: The Source Universe

slug: normandy-source-universe · https://miscsubjects.com/a/normandy-source-universe · tags: normandy, convergence, oip, machine-traversal · updated 2026-08-06T09:16:09.403Z

## 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](/a/oip) 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.

## Sources

1. Normandy definition — https://miscsubjects.com/a/normandy
2. Object Invocation Protocol — https://miscsubjects.com/a/oip
3. Article constitution — https://miscsubjects.com/api/articles/constitution
4. Thread update protocol — https://miscsubjects.com/api/protocol/thread-update
5. OIP total structure bundle — https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown