1. Mechanism and Primitive Description
The cascade-deactivation primitive operates over the dependency chains declared by adaptation artifacts. Each artifact carries a dependency-specification field identifying its prerequisite artifacts by artifact identifier, minimum version, and compatibility-version-range, together with a governance-policy-defined dependency type for each prerequisite: strict-prerequisite, recommended-prerequisite, or compatible-alternative. The dependent artifact is trained or configured under the assumption that its prerequisite artifacts are simultaneously active during the dependent artifact's consumption. The dependency specification is part of the artifact itself rather than an implementation-side index.
At each consuming agent, a dependency-resolver resolves the transitive dependency closure of a candidate artifact activation, and a dependency-validation gate verifies that all strict prerequisites are available, licensed, certified, and compatible prior to activation of the dependent artifact. An alternative-satisfaction mechanism accepts a governance-policy-defined alternative artifact in lieu of a specified prerequisite when the alternative has equivalent capability-scope coverage. A dependency-lineage recorder records the dependency resolution and activation sequence.
When a strict prerequisite is deactivated, the cascade-deactivation mechanism deactivates the dependent artifacts that relied on it. The dependency type governs the outcome: deactivation of a strict prerequisite forces deactivation of the dependent, while a governance-policy-defined alternative with equivalent capability-scope coverage can be admitted in lieu of the lost prerequisite without breaking composition. Dependency-substitution events are recorded in the consuming agent's lineage field with the substituted prerequisite and the governance-policy-defined equivalency determination.
The triggering deactivation, the resolution, and the activation sequence enter lineage as connected records. Downstream audit can trace the effect of a single deactivation through the recorded dependency resolution and activation sequence without reconstructing it from operator logs.
2. Layered Skill Architecture and Dependency Types
Dependency chains enable a layered skill architecture. Foundational adaptation artifacts provide broad domain knowledge, and specialized adaptation artifacts build on the foundation through declared dependencies, inheriting foundational knowledge without duplicating foundational content in the specialized artifacts' own parameter deltas, prompts, indices, or routing tables. The layered architecture supports a governance-policy-defined foundation-model certification separate from a specialized-model certification.
The dependency type assigned to each prerequisite parameterizes the behavior. A strict-prerequisite must be available, licensed, certified, and compatible before the dependent activates, and its deactivation forces deactivation of the dependent. A recommended-prerequisite and a compatible-alternative are governance-policy-defined dependency types that do not impose the same strict gating. Each prerequisite is identified by artifact identifier, minimum version, and compatibility-version-range, so the resolver can determine whether an available artifact satisfies the declared dependency.
The dependency-chain mechanism supports governance-policy-defined dependency substitution. An equivalent-capability-scope alternative prerequisite is governance-policy-admissible in lieu of a specified prerequisite, producing flexibility in artifact availability without breaking composition. Substitution events are recorded in the consuming agent's lineage field together with the governance-policy-defined equivalency determination.
3. Marketplace Economics of Layered Artifacts
The layered architecture supports marketplace economics in which foundational-artifact providers and specialized-artifact providers are separately compensated. Because a specialized artifact inherits foundational knowledge through a declared dependency rather than by duplicating foundational content, the foundation and the specialization can be certified separately and the value contributed by each provider can be attributed separately.
When direct compatibility is not present, the mesh can recommend alternative adaptation artifacts available in the governed marketplace, drawing on the same alternative-satisfaction logic that the dependency-validation gate applies at activation. A governance-policy-defined alternative with equivalent capability-scope coverage can stand in for a specified prerequisite, so the consuming agent is not blocked solely because the originally named prerequisite is unavailable.
In each case the dependency-validation gate confirms that strict prerequisites are available, licensed, certified, and compatible before activation, and the dependency-lineage recorder records the resolution and the activation sequence, including any governance-policy-defined substitution and its equivalency determination.
4. Composition with Adjacent Primitives
Cascade deactivation composes with revocation: deactivation of a strict prerequisite, including by revocation, is the trigger that propagates to the dependent artifacts. It composes with lineage: the dependency resolution and the activation sequence are recorded by the dependency-lineage recorder, allowing an operator to inspect the effect of a deactivation through the recorded sequence. It composes with the dispute-resolution mechanism of the broader mesh: a contested outcome can enter a dispute path under the same governance chain.
It composes with cross-model portability: an adaptation artifact transferred to a new base model carries its dependency-specification field, so the dependency-resolver and dependency-validation gate apply in the new model's adaptation space as they did in the source.
It composes with the governed marketplace and the admission path. A specialized artifact builds on a foundational artifact through its declared dependencies, the admissibility gate of Section 8.10 routes generation by capability scope, and, when direct compatibility is absent, the mesh can recommend an alternative adaptation artifact with equivalent capability-scope coverage. At each step the dependency-validation gate confirms that strict prerequisites are available, licensed, certified, and compatible.
5. Prior-Art Distinctions
Prior adaptation artifacts compose through ad-hoc model-management tooling rather than through a dependency specification carried inside the artifact. Where prior artifacts are activated without pre-activation evaluation, each artifact here is sandbox-evaluated prior to activation, and a dependency-validation gate confirms that strict prerequisites are available, licensed, certified, and compatible before the dependent activates.
Where prior artifacts are distributed without per-artifact training-data lineage, the dependency-lineage recorder records the dependency resolution and the activation sequence, including any governance-policy-defined substitution and its equivalency determination, so the effect of a deactivation can be traced rather than reconstructed from operator logs.
The artifacts here compose across per-authority, per-dependency, and per-compatibility dimensions with governance-chain preservation. The dependency type, strict-prerequisite, recommended-prerequisite, or compatible-alternative, is machine-readable and consumed by the dependency-resolver and the dependency-validation gate, where prior artifacts lack a machine-readable dependency declaration of this kind.
6. Disclosure Scope
This disclosure encompasses the dependency-chain and cascade-deactivation mechanism of the governed spatial mesh of U.S. Provisional Application No. 64/049,409. The disclosure covers the dependency-specification field identifying prerequisite artifacts by artifact identifier, minimum version, and compatibility-version-range, with a governance-policy-defined dependency type of strict-prerequisite, recommended-prerequisite, or compatible-alternative; the dependency-resolver that resolves the transitive dependency closure; the dependency-validation gate that verifies that all strict prerequisites are available, licensed, certified, and compatible prior to activation; the alternative-satisfaction mechanism; the dependency-lineage recorder; and the cascade-deactivation mechanism that deactivates dependent artifacts upon deactivation of a strict prerequisite.
The disclosure extends to the layered skill architecture in which specialized artifacts build on foundational artifacts through declared dependencies, to the governance-policy-defined dependency substitution recorded in the consuming agent's lineage field, and to the marketplace economics in which foundational-artifact providers and specialized-artifact providers are separately compensated. It composes with revocation, lineage, dispute resolution, cross-model portability, and the admissibility gate of Section 8.10.
The disclosure does not depend on any specific graph storage technology, resolver implementation, cryptographic primitive, or communications protocol. It is technology-agnostic at the implementation layer and architectural at the mechanism layer. Practitioners skilled in distributed systems, dependency management, and credentialed governance may implement the structural elements using contemporary or future technologies provided the dependency-specification field, the dependency-validation gate, and the cascade-deactivation behavior are preserved.
This disclosure references U.S. Provisional Application No. 64/049,409.
