Normandy: The Convergence Delta

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-convergence-delta
Title: Normandy: The Convergence Delta

Focus: Explain convergence delta: distant fields using different language but describing the same operation. Show why Normandy pages must expose source distance, shared structure, what each source saw, what each missed, falsifier, and OIP implication.

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 BRIE

{
  "slug": "normandy-convergence-delta",
  "title": "Normandy: The Convergence Delta",
  "body": "## Claim\n\nConvergence delta is the measurable distance between two or more sources that use different language yet describe the same operation. Normandy pages expose this distance by recording what each source saw, what each source missed, the shared structure underneath the language, the falsifier for the mapping, and the OIP implication that follows from the mapping.\n\n## Object shape\n\nThe object is an article record with these fields: slug, title, body (readable prose), claims array (atomic assertions), sources array (with id, url, quote, summary), register (source_ledger), and OIP metadata (invocation id, receipt id). The object is retrieved by GET /a/<slug> or POST /api/dispatch with invoke key. Every field is written once, appended to the ledger, and returned as a receipt at /api/dispatch?receipt=inv_ID. The object carries no negation language and no comparison language outside explicit comparison articles.\n\n## Source lineage\n\nThe lineage starts at https://miscsubjects.com/a/normandy which defines the landing surface that converts source universes into linked article objects. It continues at https://miscsubjects.com/a/oip which defines the unit as the work object, the proof as the receipt, and the loop as object-invoke-ledger-receipt-replay-repair. It extends throug