Admissibility as Skill Router
by Nick Clark | Published April 25, 2026
Operating units route incoming requests to applicable skills through admissibility evaluation. The admissibility profile, rather than capability matching alone, determines which skill handles each request.
What It Specifies
Each skill declares its admissibility profile: applicable operating environments, required credentials, required attestations, applicable jurisdictions. Incoming requests admit against profiles; admissible skills handle requests; non-admissible skills are excluded from routing.
Routing decisions enter lineage. The triggering request, the evaluated skills, the admissibility outcomes, and the routing result all enter audit retention.
Why It Matters Structurally
Capability-only routing produces architectural risk. Skills capable of handling requests may not be admissible in the operating context; capability without admissibility produces unauthorized skill activation.
Admissibility-driven routing produces structural support. Skills admit only when applicable; routing is governed by the operating context; unauthorized skill activation is structurally prevented.
How It Composes With Mesh Operation
The architecture defines the admissibility-profile format, the routing-evaluation primitives, and the routing-decision recording. Implementations apply the architecture; skill routing operates within the framework.
Routing composes with other features. Cross-jurisdictional routing, byzantine-robust routing under disputed profiles, and dispute mechanism for routing disputes all build on the routing primitive.
What This Enables
Defense adaptation operations gain structurally-supported routing. Civilian critical-infrastructure adaptation operations gain the same.
The architecture also supports routing evolution. As skill ecosystems mature, routing patterns update through governance procedures.
