{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-signed-skill-manifest-that-validates-but-resolves-to-a-different-callable-than-the-one-authorized",
  "title": "In what scenarios must an instance reject a signed skill manifest that validates but resolves to a different callable than the one authorized",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent runtimes that dynamically load skills/tools from a registry where manifests are signed and entries are resolved by name at invocation time. Does not apply to statically linked tool sets or to registries where the manifest embeds the full callable body rather than a reference.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-signed-skill-manifest-that-validates-but-resolves-to-a-different-callable-than-the-one-authorized.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-signed-skill-manifest-that-validates-but-resolves-to-a-different-callable-than-the-one-authorized.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-signed-skill-manifest-that-validates-but-resolves-to-a-different-callable-than-the-one-authorized.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1583,
    "python_slice_tokens": 267,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A signed manifest attests to *the content of a declaration*, not to *the identity of the code that will execute on resolution*. The boundary failure lives in the gap between two distinct integrity properties: 1. **Manifest integrity** — the bytes of the manifest were produced by a holder of the signing key and have not been altered. This is what signature ve...",
    "what_was_observed": "In a multi-tenant agent deployment, skill manifests were Ed25519-signed at publish time. Each manifest declared `entrypoint: \"skills.<name>:run\"` and a `sha256` of the manifest body. Verification was performed at load time and passed for every manifest. Nevertheless, a tenant was able to invoke another tenant's privileged skill. The mechanism was namespace shadowing. Skill modules were imported by dotted path against...",
    "condition_of_validity": "The rejection requirement holds precisely when **all** of the following are true: - The manifest references the callable indirectly (by symbol, dotted path, alias, or registry key) rather than embedding the callable body or a content hash of the resolved artifact. - The resolution namespace (import path ordering, alias table, plugin directory) is mutable aft...",
    "decision_boundary": "The decision is not \"is the signature valid\" but \"does the signed declaration uniquely determine the executing callable under the current namespace.\" Concretely, an instance must reject the load when any of these hold: - The resolved callable's origin (module file path, inode, or content hash) differs from the origin recorded at signing time, or no origin wa...",
    "operational_effect": "Treating signature validity as sufficient produces a false sense of integrity: audit logs show \"manifest verified\" for every injected skill, so incident response systematically under-scopes the blast radius and attributes compromise to key theft rather than namespace manipulation. The corrective posture is to make resolution a first-class, signed, verified s..."
  },
  "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": "98b08407e1e7aece3421db5c9fc12af3007a5ff18a5aabb7a7c40a748adc5665",
    "verified_classes": [
      "ResolutionIntegrityError",
      "SignedManifest"
    ],
    "verified_functions": [
      "resolve_origin_hash",
      "authorize_and_resolve"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ResolutionIntegrityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
