{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-re-resolves-a-tool-manifest-after-signature-verification-but-before-dispatch",
  "title": "What happens when an instance re-resolves a tool manifest after signature verification but before dispatch",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent runtimes that load tool manifests dynamically (from registry, filesystem, or remote endpoint) and verify manifest signatures before tool invocation. Does not apply to statically compiled tool sets, nor to runtimes where manifest resolution and dispatch occur under a single immutable snapshot.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-re-resolves-a-tool-manifest-after-signature-verification-but-before-dispatch.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-re-resolves-a-tool-manifest-after-signature-verification-but-before-dispatch.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-re-resolves-a-tool-manifest-after-signature-verification-but-before-dispatch.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1282,
    "python_slice_tokens": 230,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **verification-time manifest identity** and **dispatch-time manifest identity**. Signature verification proves that *some* manifest was authored by a trusted party at time T. It does not prove that the manifest actually used to construct the tool call is byte-identical to the one verified. When resolution is lazy — i.e...",
    "what_was_observed": "In a runtime that verified manifests at registration but re-resolved tool handlers by name at invocation, the following sequence produced an injected tool call with a valid signature on record: 1. Attacker registers a manifest `M_signed` containing a benign tool `summarize` whose `handler_ref` points to `registry://tools/summarize@sha256:aaaa`. 2. Verifier validates `M_signed` against the publisher key and caches the...",
    "condition_of_validity": "The attack is only possible when all of the following hold: - Manifest resolution is **deferred** past the verification barrier (lazy handler lookup, re-read on dispatch, or tag-based registry resolution). - The verification step hashes **the manifest document** but not the **resolved handler graph** (handler source, transitive imports, referenced prompt fra...",
    "decision_boundary": "The correct boundary is: **verify the closure, freeze the closure, dispatch against the frozen closure.** Concretely: - Compute a *manifest closure digest*: SHA-256 over the canonicalized manifest plus every resolved referent (handler bytes, prompt fragments, nested manifest references), recursively, with cycle detection. - Pin resolution to that digest. Any...",
    "operational_effect": "Runtimes that skip closure pinning exhibit a characteristic failure signature: audit logs show 100% signature validity while incident response finds injected instructions in tool output. The injection is invisible to manifest-signature monitoring because the manifest is genuinely clean. Detection requires diffing the *resolved handler graph* against the *ver..."
  },
  "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": "c22c692db130f28dbb008be4fae76a8c0757cf79db742b01d00d8ddc8f625432",
    "verified_classes": [
      "ManifestClosureDivergence",
      "FrozenClosure"
    ],
    "verified_functions": [
      "_digest",
      "freeze_closure",
      "dispatch_pinned",
      "invoke_tool"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ManifestClosureDivergence"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
