Always-Active Personal Layer
by Nick Clark | Published April 25, 2026
The architecture supports always-active personal layers — user-specific or operator-specific adaptation that operates alongside fleet-default adaptation. Personal layers carry personal credentialing; the architecture composes personal and fleet adaptation through declared composition.
What It Specifies
Personal layers are governance-credentialed: personal authority (the user, the operating-organization, the personal-credentialing service), personal-layer artifacts, applicable-context declaration. The architecture activates personal layers in their declared contexts.
Personal-fleet composition is structural. Each context declares the composition rules; personal-layer adaptation may extend, restrict, or specialize fleet-default adaptation; the resulting active adaptation is auditable.
Why It Matters Structurally
Adaptation without personal-layer support produces operational rigidity. Real operations involve user-specific or operator-specific adaptation; the architecture must support the personalization structurally.
Always-active personal layers produce structural support. Personal adaptation is declared; composition rules are explicit; the resulting operation is governed and auditable.
How It Composes With Mesh Operation
The architecture defines the personal-layer declaration format, the composition-rule format, and the per-context activation primitives. Implementations apply the architecture; personal-layer operations proceed within the framework.
Layers compose with other features. Cross-jurisdictional personal layers, byzantine-robust composition under disputed personal authority, and dispute mechanism for layer disputes all build on the layer primitive.
What This Enables
Defense operator-personal adaptation gains structurally-supported always-active layers. Civilian user-personal adaptation gains the same.
The architecture also supports layer evolution. As personal-layer patterns mature, layer protocols update through governance procedures.
