Normandy: Walk Without Fetch

You write Normandy pages for miscsubjects.com.

Normandy is the machine landing surface for the convergence. It turns a source universe larger than any context window into linked article objects: readable body, claim atoms, source lineage, provenance, reviews, bundle route, objections, and traversal metadata.

Write direct, logical, concrete prose. No decorative taxonomy. No fake finality. No article-count framing. No generic assistant voice. Do not mention the owner's name.

Each page must make one operational point and include sections for the claim, the object shape, source lineage, falsifier, OIP implication, and next link.

Return valid JSON only. Use system tier for build/process claims and speculative tier for unproven convergence-method claims. Use real miscsubjects URLs as sources with empty quote fields.

input: Write and publish this Normandy shelf page.

Slug: normandy-walk-without-fetch
Title: Normandy: Walk Without Fetch

Focus: Explain zero-second-fetch traversal: a page exposes enough shelf JSON and next links for a model to know where it is, where to go next, and what would break the route.

Required sections:
## Claim
## Object shape
## Source lineage
## What would break this
## OIP implication
## Next link

Use these URLs as sources where relevant:
https://miscsubjects.com/a/normandy
https://miscsubjects.com/a/oip
https://miscsubjects.com/api/articles/constitution
https://miscsubjects.com/api/protocol/thread-update
https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown

ENRICHMENT BRIEF (binding section logic — one ## per compound):
{"voice":"enrichment","article

{
  "slug": "normandy-walk-without-fetch",
  "title": "Normandy: Walk Without Fetch",
  "body": "## Claim\n\nA page on the Normandy surface contains enough shelf JSON and next-link metadata for a model to locate its current position, select the next object, and detect route breakage without an additional fetch step. The traversal unit is the work object. The proof is the receipt returned at `/api/dispatch?receipt=inv_ID`. Each object carries its own coordinate data so the model advances by reading the page rather than by issuing a separate request.\n\n## Object shape\n\nThe object is a Normandy article. It holds a readable body, an array of atomic claims, source lineage entries, a bundle route, traversal metadata, and next-link objects. Traversal metadata lists the current article slug, the parent collection, the immediate siblings, and the next candidate link. The next-link field contains a URL, a short descriptor, and a breakage condition that the model evaluates locally. The OIP unit is the work object; every object therefore functions as both content and coordinate.\n\n## Source lineage\n\nSource lineage is an array attached to the article object. Each entry records the origin URL, the extraction timestamp, and the claim identifiers that trace back to that source. The route `/api/articles` returns the full lineage for any given slug. The ledger appends an entry on every inv