---
slug: normandy-convergence-delta
title: Normandy: The Convergence Delta
canonical: https://miscsubjects.com/a/normandy-convergence-delta
---

## Claim

Convergence 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.

## Object shape

The 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.

## Source lineage

The 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 through https://miscsubjects.com/api/articles/constitution which lists the article fields and their required order. It continues at https://miscsubjects.com/api/protocol/thread-update which records each append operation to the ledger. It terminates at https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown which supplies the bundle route for retrieving the complete structure in one response. Each URL is recorded with its exact contribution and its exact omission.

## What would break this

The mapping breaks if any source omits the receipt field, if the ledger append fails to return an inv_ID, if two sources assign the same operation to different receipt routes, or if a later source rewrites a prior source's language without preserving the original claim id. The mapping also breaks if the falsifier test returns a receipt that contradicts the shared structure asserted in the claims array.

## OIP implication

OIP treats convergence delta as an operation that must be invoked, ledgered, receipted, and replayed. POST /api/dispatch {key: "normandy-convergence-delta", body: {sources: ["https://miscsubjects.com/a/normandy", ...]}} appends the delta record to the ledger and returns a receipt at /api/dispatch?receipt=inv_ID. The receipt contains the source distance, the shared structure, the falsifier, and the next link. Any later replay uses the receipt id to restore the exact state that existed at the time of the first dispatch.

## Next link

The next link is the article that records the first concrete convergence delta between two named sources. Its slug is derived from the two source slugs joined by a hyphen. The object is invoked through the same POST /api/dispatch route and follows the same receipt rule.
