{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-signed-skill-registry-pass-verification-yet-execute-unregistered-code-the-descriptor-vs-payload-split-in-dynamic-agent-skill",
  "title": "Why does an instance of a signed skill registry pass verification yet execute unregistered code: the descriptor-vs-payload split in dynamic agent skill loading",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent runtimes that load tools/skills from a registry where registry entries are cryptographically signed (Sigstore/cosign, in-toto attestations, or detached signatures) but the loaded skill's *executable payload* is resolved at load time via a mutable reference (URL, path, package specifier, or environment-dependent import). Does not apply to fully hermetic registries where the signature covers the exact bytes executed and the resolver is content-addressed.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-signed-skill-registry-pass-verification-yet-execute-unregistered-code-the-descriptor-vs-payload-split-in-dynamic-agent-skill.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-signed-skill-registry-pass-verification-yet-execute-unregistered-code-the-descriptor-vs-payload-split-in-dynamic-agent-skill.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-signed-skill-registry-pass-verification-yet-execute-unregistered-code-the-descriptor-vs-payload-split-in-dynamic-agent-skill.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1505,
    "python_slice_tokens": 214,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious failure is a **signature-subject mismatch between the skill descriptor and the skill payload**. Signing systems are usually applied to the *descriptor* — the manifest that names the skill, declares its entrypoint, permissions, and dependency set. The verifier checks that manifest. But the runtime then *resolves* the entrypoint (a `pip` specif...",
    "what_was_observed": "In a representative dynamic skill registry, a manifest `skill.yaml` is signed with cosign and stored alongside an OCI artifact. The manifest contains: Verification passes because `skill.yaml` is byte-identical to the signed copy. Execution then proceeds: the runtime activates a virtualenv, runs `pip install 'docparse>=2.0,<3'`, and imports `skills.summarize`. Three independent swaps are possible *after* verification:...",
    "condition_of_validity": "The attack requires the conjunction of: - **Loose resolution**: the entrypoint or any transitive dependency is resolved by a *range, tag, name, or path* rather than a content digest. - **Ambient authority**: the resolver consults mutable state the attacker can influence — working directory, `PYTHONPATH`/`NODE_PATH`, search roots, package index, or a cache di...",
    "decision_boundary": "Operationally, treat a skill as **loadable** only when all of the following hold; otherwise treat it as **untrusted and refuse activation**: - The attestation's subject set includes a digest of the *resolved* payload (module file hash or wheel digest), not only the manifest. - Every dependency is pinned to an exact version *and* that version's digest is pres...",
    "operational_effect": "When the gate is placed at resolution, the failure mode changes from *silent payload substitution under a green check* to *explicit refusal with a hash mismatch*, which is auditable and alertable. The cost is that lazy, per-call resolution must become eager, pinned resolution — a latency and cache-management change, and a hard requirement that the registry p..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "6b900d4a77ebdb9dd7d62a8c44b5e71f620a996e397a0a8554f30e5124f61703",
    "verified_classes": [
      "SkillResolutionError",
      "Attestation"
    ],
    "verified_functions": [
      "_hash_bytes",
      "activate_skill"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SkillResolutionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
