{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-dynamically-registered-skill-escape-provenance-checks-when-its-manifest-is-re-signed-during-hot-reload",
  "title": "Why does an instance of a dynamically registered skill escape provenance checks when its manifest is re-signed during hot reload",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent runtimes that permit runtime registration of tools/skills from external manifests and that verify manifest signatures at load time but cache the resolved callable by skill name. Does not apply to runtimes that re-verify provenance on every invocation, or to statically compiled tool registries with no hot-reload path.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-registered-skill-escape-provenance-checks-when-its-manifest-is-re-signed-during-hot-reload.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-registered-skill-escape-provenance-checks-when-its-manifest-is-re-signed-during-hot-reload.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-registered-skill-escape-provenance-checks-when-its-manifest-is-re-signed-during-hot-reload.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1381,
    "python_slice_tokens": 199,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not in signature verification. Signature verification works correctly. The failure is in the *binding lifetime* between a verified manifest and the executable skill object it authorizes. Most runtimes treat \"manifest verified\" as a property of the *registration event*, not of the *invocation event*. When a skill is hot-reloaded — because a man...",
    "what_was_observed": "In a runtime with a plugin registry keyed by `skill_name`, a skill `summarize_docs` was registered with a manifest declaring capabilities `{read:docs}` and a signed provenance record. The agent's policy engine cached the decision `allow(summarize_docs, read:docs)` keyed on the string `summarize_docs`. A publisher pushed an updated manifest for the same skill name, declaring capabilities `{read:docs, net:egress, exec:...",
    "condition_of_validity": "This boundary applies when all of the following hold: (1) skills are addressable by a stable name that outlives individual manifest versions; (2) authorization decisions are cached or memoized to avoid re-evaluating policy on each call; (3) the cache key does not include the manifest digest or a content hash of the callable; (4) hot reload permits replacing ...",
    "decision_boundary": "The correct decision boundary is: **re-evaluate policy against the declared capability set whenever the manifest digest changes, regardless of whether the skill name or publisher identity is unchanged.** Operationally, this means the authorization cache key must be `(skill_name, manifest_digest)`, and the hot-reload path must treat a digest change as a cache...",
    "operational_effect": "After applying digest-keyed authorization caching and superset-triggered re-approval, the `summarize_docs` reload produced a cache miss, the policy engine evaluated the new capability set `{read:docs, net:egress, exec:shell}`, and the agent's policy denied `net:egress` and `exec:shell` for that skill class, blocking the exfiltration. The cost is additional 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": "0a993cf601b3f4503a21aceb1e7e807aeb644301c824381d7867c485963c4230",
    "verified_classes": [
      "SkillProvenanceError",
      "Manifest",
      "AuthorizationCache"
    ],
    "verified_functions": [
      "invoke_skill",
      "digest",
      "grant",
      "lookup"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SkillProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
