{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-verified-agent-plugin-fail-provenance-re-attestation-after-a-benign-dependency-upgrade",
  "title": "Why does an instance of a verified agent plugin fail provenance re-attestation after a benign dependency upgrade",
  "date_of_record": "2026 November 16",
  "scope": "This record applies to agent plugin runtimes that enforce skill provenance via signed attestations (in-toto/SLSA-style) and re-verify on every load or upgrade. It does not apply to runtimes that pin immutable digests and never re-resolve dependency graphs, nor to plugins whose attestations bind only to a top-level artifact hash.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-verified-agent-plugin-fail-provenance-re-attestation-after-a-benign-dependency-upgrade.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-verified-agent-plugin-fail-provenance-re-attestation-after-a-benign-dependency-upgrade.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-verified-agent-plugin-fail-provenance-re-attestation-after-a-benign-dependency-upgrade.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1070,
    "python_slice_tokens": 174,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: **provenance attestation verifies the identity of the builder and the inputs it *declared*, not the inputs the runtime *resolved*.** A plugin can carry a perfectly valid signature over an SBOM that lists `libfoo==2.3.1`, while the runtime, at load time, resolves `libfoo==2.3.4` because the plugin's requirement was `libfoo>=...",
    "what_was_observed": "During a routine dependency refresh, a plugin `skill:summarize-v2` was upgraded from `libfoo 2.3.1` to `2.3.4` (a transitive patch bump pulled in by an unrelated requirement). The loader performed, in order: 1. Signature check over the attestation envelope — **passed**. 2. Builder identity check against the trusted builder set — **passed**. 3. SBOM digest comparison against the *declared* SBOM in the attestation — **...",
    "condition_of_validity": "Re-attestation is only sound when the following holds: - The runtime resolves a **complete, closed** dependency set before verification, and - The attestation binds to the **resolved digest set**, not to a declared manifest, and - The comparison is **set equality** between attested and resolved artifacts (or a signed lockfile whose digest is itself attested)...",
    "decision_boundary": "The boundary is crossed the moment a version range (`>=`, `~=`, `^`) is permitted to resolve to a different artifact than the one attested. At that point: - **Below the boundary** (pinned digests, lockfile attested as a unit): re-attestation is a pure hash comparison and cannot drift. Fail closed on any mismatch. - **At the boundary** (ranges allowed, manife...",
    "operational_effect": "After this incident the loader was changed to compute the resolved artifact digest set, canonicalize it, and compare against the attested set with strict equality; any delta raises a provenance error and blocks load pending re-attestation. Benign upgrades now fail loudly and require the publisher to re-sign — a deliberate availability-for-integrity trade. Th..."
  },
  "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": "4d074113dfe7e91fed9e23b21c79846e4deb0c0877d7195a1ac4136daf9e3948",
    "verified_classes": [
      "ProvenanceDriftError",
      "Attestation"
    ],
    "verified_functions": [
      "canonical_digest",
      "verify_resolved_set"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ProvenanceDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
