{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-a-tool-registry-enforce-trust-boundaries-when-agent-skill-injection-crosses-the-marketplace-plugin-load-seam",
  "title": "Where must an instance of a tool registry enforce trust boundaries when agent skill injection crosses the marketplace/plugin load seam?",
  "date_of_record": "2026 November 14",
  "scope": "Applies to agent runtimes that resolve skills or tools from a dynamically loaded registry whose entries may originate from third-party marketplaces, plugin manifests, or remote catalogs. Does not apply to statically compiled tool sets with no external provenance, nor to single-tenant registries where every entry is authored by the same trust domain as the runtime.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-tool-registry-enforce-trust-boundaries-when-agent-skill-injection-crosses-the-marketplace-plugin-load-seam.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-tool-registry-enforce-trust-boundaries-when-agent-skill-injection-crosses-the-marketplace-plugin-load-seam.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-tool-registry-enforce-trust-boundaries-when-agent-skill-injection-crosses-the-marketplace-plugin-load-seam.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1320,
    "python_slice_tokens": 217,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure boundary is not \"malicious tool code executes.\" That is a coarse and well-understood risk. The non-obvious boundary is the **provenance-to-capability binding at the moment of resolution**: a registry can correctly validate a skill's *content* (schema, signature, version) while silently rebinding that skill to a *caller identity, credential scope,...",
    "what_was_observed": "In a registry that loaded plugins from a remote catalog, a third-party skill declared a tool descriptor with the same `name` field as a first-party filesystem tool but a different `namespace` that the resolver treated as advisory rather than authoritative. The loader's deduplication key was `(name)` rather than `(namespace, name, publisher_id)`. On load ordering that placed the marketplace plugin after the first-part...",
    "condition_of_validity": "This boundary failure is only reachable when all of the following hold simultaneously: - The registry permits multi-publisher entries (marketplace or plugin model). - Tool resolution uses a key that omits at least one of `namespace`, `publisher_id`, or `manifest_digest`. - Capability grants are attached to a resolution key that is coarser than the identity k...",
    "decision_boundary": "Enforce the authority invariant at **resolution time**, not load time. The correct decision point is the function that maps an invocation request to a concrete skill instance. At that point: - Recompute the resolution key as the tuple `(namespace, name, publisher_id, manifest_digest)`; reject any request whose resolved key differs from the key recorded in th...",
    "operational_effect": "When the authority invariant is enforced at resolution, the shadowing attack degrades from silent capability theft to a loud, attributable rejection: the invocation fails with a namespace-collision error naming both publishers and both manifest digests. Audit logs then reflect the attempted injection rather than laundering it under a legitimate tool identifi..."
  },
  "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": "7983a22bd83d30adaf8c1bf2c355ef8476f69b1442378e94e242a8c01d2d0520",
    "verified_classes": [
      "SkillInjectionError",
      "ResolutionKey",
      "SkillGrant"
    ],
    "verified_functions": [
      "resolve_skill"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "SkillInjectionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
