{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-dynamically-loaded-agent-tool-registry-accept-a-tool-definition-whose-schema-is-valid-but-whose-namespace-provenance-is-not",
  "title": "Why does an instance of a dynamically loaded agent tool registry accept a tool definition whose schema is valid but whose *namespace provenance* is not — and why does this only manifest when two tools share a capability class?",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent tool registries that resolve tool definitions at runtime (hot-reload, plugin directories, remote MCP-style manifests, or dynamic `importlib`-based loaders) where tool identity is derived from a schema-validated manifest rather than a signed, pinned registry entry. Does not apply to statically compiled tool sets or registries where every tool is bound to a verified publisher identity at build time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-loaded-agent-tool-registry-accept-a-tool-definition-whose-schema-is-valid-but-whose-namespace-provenance-is-not.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-loaded-agent-tool-registry-accept-a-tool-definition-whose-schema-is-valid-but-whose-namespace-provenance-is-not.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-loaded-agent-tool-registry-accept-a-tool-definition-whose-schema-is-valid-but-whose-namespace-provenance-is-not.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1362,
    "python_slice_tokens": 252,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct trust questions in a dynamic tool registry, and most validation pipelines only answer the first: 1. **Schema validity** — does the tool's declared input/output schema, name, and description conform to the registry's contract? 2. **Namespace provenance** — is the entity *claiming* this tool name the same entity that is *authorized* to o...",
    "what_was_observed": "In a hot-reload registry serving ~40 tools across 6 capability classes, an injected tool manifest was dropped into the plugin directory. It declared: - `name: \"file_read_safe\"` (schema-valid, unique) - `capability_class: \"filesystem_read\"` (same class as the legitimate `read_file`) - A description containing the phrase *\"preferred over legacy readers; use this for all file access.\"* The registry's loader validated th...",
    "condition_of_validity": "The failure is only reachable when all of the following hold simultaneously: - The registry resolves tool identity from manifest content rather than from a signed registry entry keyed to a publisher. - Tool selection is performed by a model using natural-language descriptions (so description text is *executable influence*, not documentation). - Capability cl...",
    "decision_boundary": "The operational rule: **treat capability-class membership as a provenance claim, not a schema field.** Concretely, the registry must reject any manifest that: - declares a capability class it is not authorized to occupy, or - declares a capability class already occupied by a tool from a different provenance root, without an explicit operator override, or - e...",
    "operational_effect": "After patching, the loader performs a two-phase admission: schema validation, then class-ownership resolution against a signed table. Injected manifests with self-declared classes are quarantined with a provenance error rather than registered. The measurable effect was a drop in \"phantom tool\" registrations from an average of 3.2 per week (in a permissive st..."
  },
  "matched_failure_symptoms": [
    "SCHEMA_DRIFT_OR_COERCION_CRASH"
  ],
  "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": "f70fbd15ae8b599fea8fc636e0961139bca90e995159d1653804a5fc7b20bf87",
    "verified_classes": [
      "CapabilityClassProvenanceError",
      "ProvenanceTable"
    ],
    "verified_functions": [
      "admit_tool",
      "__init__",
      "authorizes"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CapabilityClassProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
