Cross-Model Adaptation Portability
by Nick Clark | Published April 25, 2026
Adaptations port across underlying models through credentialed translation. An adaptation built for one base model carries declared portability metadata; cross-model translators produce adaptations applicable to alternative base models.
What It Specifies
Portability translators are governance-credentialed: source-model declaration, target-model declaration, translation rules, validation requirements. Cross-model adaptations admit against the portability translation.
Translation events enter lineage. The source adaptation, translator identity, target adaptation, and any translation ambiguity all enter the cross-model adaptation's lineage.
Why It Matters Structurally
Adaptations without portability faces structural lock-in. Adaptations built for specific base models cannot transfer; operational evolution requires costly adaptation rebuilding.
Cross-model portability produces structural flexibility. Translators provide cross-model adaptations; the architecture supports model evolution; operational evolution becomes structurally supported.
How It Composes With Mesh Operation
The architecture defines the portability-metadata format, the translator-declaration format, and the cross-model adaptation-deployment integration. Implementations apply the architecture; cross-model operations proceed within the framework.
Portability composes with other features. Cross-jurisdictional portability, byzantine-robust translation under disputed portability, and dispute mechanism for portability disputes all build on the portability primitive.
What This Enables
Defense adaptation portability across model evolution gains structurally-supported migration. Civilian critical-infrastructure adaptation portability gains the same.
The architecture also supports portability evolution. As cross-model translation matures, portability protocols update through governance procedures.
