Cross-Mesh Reconciliation: Federation Without Consensus

Federation Today Demands Consensus or Loses Lineage

Coalition military operations require interoperability across allied forces' systems. NATO Federated Mission Networking (FMN) is the formal program; the practical reality is that lineage discontinues at every coalition boundary. A target engaged by an allied force is recorded in their system, restated in our system, with no structural link between the records.

Mergers and acquisitions face the same architecture failure at corporate scale. After a merger, the two companies' meshes (governance, identity, observation) need to compose without forcing one to abandon its architecture for the other. Current IT integration projects span years and routinely fail to preserve operating lineage.

Customs and border-control handoffs lose lineage at every boundary by design: each authority maintains independent records, with manual reconciliation when disputes arise. The architectural gap is that no current mechanism preserves credentialed lineage across authority boundaries without forcing a shared authority above both.

1. The Primitive: Taxonomy Translator + Lineage-Preserving Import

Cross-mesh reconciliation provides a credentialed taxonomy translator that maps observations from one mesh's authority hierarchy to another's. The translator is itself a credentialed observation: signed by an authority standing in both meshes (or by a coalition authority signed by both standing authorities), declaring the mapping with its scope, validity, and uncertainty.

Translated observations preserve their original lineage. An observation from mesh A imported into mesh B retains its mesh-A credential, its mesh-A lineage, and gains a mesh-B presentation through the translator. A consumer in mesh B sees the observation in mesh-B taxonomy but can walk back to the original mesh-A lineage when needed.

Import is structural, not transformative. The original observation is not rewritten; the translation is a parallel signed view. This preserves audit-grade traceability across the boundary.

2. Temporal Reconciliation Across Independent Clocks

Independently governed meshes maintain their own time consensus (Article 6: mesh-derived time). Cross-mesh reconciliation reconciles temporal references between them: an observation timestamped in mesh A's time frame is restated in mesh B's time frame through a credentialed clock-offset observation that the translating authority has signed.

The clock-offset observation is itself bounded: it specifies the time window over which the offset applies, the uncertainty of the offset, and the authorities that have ratified it. Outside the window, the offset re-evaluates; uncertainty bounds propagate through downstream observations.

Temporal reconciliation is essential because most cross-mesh disputes are time-anchored: 'when did the handoff occur,' 'in what order did these events happen,' 'is the dispute about events within the validity window.' Without credentialed temporal reconciliation, these questions devolve to manual reconstruction.

3. Divergence Detector

Two meshes federated through reconciliation may nonetheless diverge: the same observation may be recorded differently in each, the same authority may produce inconsistent observations across boundaries, the translator's mapping may produce contradictions when applied to specific observation patterns.

The divergence detector is a credentialed observation produced when the federation observes inconsistency. The observation declares what diverged (the constituent observations), under what conditions (the operating context), and with what magnitude (the disagreement). It does not resolve the divergence; it surfaces it for resolution by the relevant authorities.

Divergence-as-observation makes federation auditable. Authorities can see structurally where their meshes disagree, decide whether the disagreement is acceptable (incidental local variation), repair-able (translator update), or fundamental (the meshes are not actually federable in this scope).

4. Intentional Disconnect as a First-Class Mode

Coalition partners frequently choose to disconnect their meshes for security, sovereignty, or operational reasons. The current architecture treats disconnection as failure; the governed primitive treats it as a first-class mode.

Intentional disconnect is itself a credentialed observation: the disconnecting authority publishes a credentialed disconnect notice with scope (which observations are partitioned), duration (until-when the disconnect persists), and reason (why the disconnect is desirable). Federated meshes record the disconnect and adjust their views accordingly.

When the disconnect ends, the partitioned observations during the disconnect window are reconciled through the standard taxonomy-translation and divergence-detection mechanisms. The disconnect was not data loss; it was an authority-bounded operating mode that the federation tolerated structurally.

5. Partitioned-Operation Interface

Even within a single mesh, network partitions occur. Cross-mesh reconciliation provides a partitioned-operation interface that handles intra-mesh partitions through the same architectural mechanism as inter-mesh disconnects.

The interface lets a partitioned mesh fragment continue operating with full credentialed authority within its partition: observations produced during partition are signed and admitted normally, with the partition itself being a credentialed observation that participants record. When the partition heals, observations from each fragment reconcile through the divergence detector.

This unifies the architectural treatment of partition and federation. A federation between two cooperating meshes and a partition within a single mesh use the same primitives, simplifying the trust model and reducing implementation surface.

6. Federation Without a Shared Consensus Protocol

Conventional federation approaches force a shared consensus protocol: the federated meshes must agree on a shared authority hierarchy, a shared transaction-ordering mechanism, or a shared blockchain. Each adoption is structurally expensive and concentrates authority in the consensus mechanism.

The governed primitive operates without shared consensus. Each mesh runs its own time consensus (Article 6), its own authority hierarchy, its own observation lineage. Federation occurs through credentialed translators and divergence detectors that bridge between meshes without forcing them to merge.

This is the architectural distinction from blockchain-based interoperability solutions (Cosmos IBC, Polkadot XCM, Wormhole) and from coalition-consensus protocols. Federation is a translation problem rather than a consensus problem.

7. Coalition Interoperability Embodiment

The coalition interoperability embodiment makes the architecture concrete. NATO partners, civil-military airspace, US-allied border operations all face the federation problem at scale. Each partner maintains its own mesh; the coalition operates through credentialed translators between them.

Sensitive observations stay sovereign: a partner's classified observation is admitted into its own mesh under its own credential, translated to a coalition-shareable equivalent through a credentialed declassification translator (signed by the originating authority and a coalition declassification authority), and the translated observation propagates while the original remains sovereign.

Coalition reform — partners joining, leaving, or changing trust relationships — is handled through credentialed authority updates rather than mesh re-architecture. The architecture survives changes in coalition composition that current stovepiped systems cannot.

8. What This Is Not

This is not Cosmos IBC, Polkadot XCM, or Wormhole. Those provide blockchain-to-blockchain bridges with shared consensus elements. The governed primitive operates without consensus.

This is not NATO FMN as currently specified. FMN is a policy framework; the governed primitive provides the architectural mechanism that could implement FMN's federation goals.

This is not enterprise data-fabric integration. Those products provide schema mapping; the governed primitive provides credentialed lineage preservation across authority boundaries.

Conclusion

Cross-mesh reconciliation provides federation between independently governed meshes through credentialed taxonomy translation, temporal reconciliation, divergence detection, intentional disconnect, and partitioned-operation interfaces — all without forcing shared consensus.

Disclosed under USPTO provisional 64/049,409, the primitive serves coalition military operations, M&A integration, customs and border handoff, civil-military airspace, and other federation cases where current architectures lose lineage at every authority boundary.