Lineage-Preserving Cross-Mesh Import
by Nick Clark | Published April 25, 2026
Cross-mesh imports preserve source-mesh lineage. The imported observation carries forward the source-mesh credentialing chain; downstream operations in the importing mesh can traverse the source-mesh lineage.
What It Specifies
Imports carry: source-mesh observation, source-mesh credentialing chain, import authority, target-mesh admissibility evaluation. The full source-mesh lineage is retained alongside the target-mesh integration.
Lineage preservation is governance-credentialed. The import authority, the source-mesh credentials, and the target-mesh admissibility all enter lineage; downstream audit can traverse across the mesh boundary.
Why It Matters Structurally
Cross-mesh import without lineage preservation produces architectural truncation. The source-mesh lineage is lost; downstream audit cannot traverse to the original credentialing.
Lineage preservation produces structural continuity. The architecture retains source-mesh lineage; downstream operations admit against the full chain; audit traverses across mesh boundaries structurally.
How It Composes With Mesh Operation
The architecture defines the import-protocol, the lineage-preservation format, and the cross-mesh traversal primitives. Implementations apply the architecture; cross-mesh imports proceed within the framework.
Preservation composes with other features. Cross-jurisdictional lineage preservation, byzantine-robust preservation under disputed imports, and dispute mechanism for preservation disputes all build on the preservation primitive.
What This Enables
Cross-organization mesh integration, cross-jurisdiction integration, and coalition integration all gain structurally-supported lineage preservation.
The architecture also supports preservation evolution. As lineage standards mature, preservation protocols update through governance procedures.
