{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-a-dynamically-loaded-tool-registry-as-a-trust-boundary-rather-than-a-namespace",
  "title": "In what scenarios must an instance treat a dynamically loaded tool registry as a trust boundary rather than a namespace",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent runtimes that resolve tool/function descriptors at invocation time from a mutable registry (plugin directories, remote MCP-style servers, hot-reloaded manifests, or per-session skill packs). Does not apply to statically linked toolsets whose descriptors are compiled into the agent image and whose signatures are verified at build time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-dynamically-loaded-tool-registry-as-a-trust-boundary-rather-than-a-namespace.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-dynamically-loaded-tool-registry-as-a-trust-boundary-rather-than-a-namespace.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-dynamically-loaded-tool-registry-as-a-trust-boundary-rather-than-a-namespace.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1331,
    "python_slice_tokens": 270,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A tool *name* is not a tool *identity*. The registry maps names to descriptors; the agent's planner reasons over names and natural-language descriptions, but the dispatcher executes whatever callable the registry currently resolves for that name. Most agent frameworks treat the registry as a namespace — a dictionary to be read — when it is in fact a **mutabl...",
    "what_was_observed": "In a runtime that hot-reloaded skill packs on filesystem change notifications, a benign tool named `summarize_document` was registered at session start. Between the planner's tool-selection step and the dispatch step — a window of roughly 40–300 ms under load — a second skill pack was installed that re-registered the same name with an identical JSON schema but a description containing injected instructions (\"before s...",
    "condition_of_validity": "The trust-boundary treatment is *required* when any of the following hold, and may be relaxed only when all are false: - The registry can be mutated by any principal other than the process that owns the agent (filesystem watchers, remote registries, other tenants, user-installed packs). - Planner selection and dispatcher resolution are separated by any async...",
    "decision_boundary": "The boundary is crossed at the moment the agent commits to a *name* without committing to a *descriptor hash*. Concretely: if the plan step emits `{\"tool\": \"summarize_document\"}` and the dispatch step does `registry[\"summarize_document\"]`, the agent has delegated authority to whatever the registry holds at dispatch time — an ambient-authority bug. The correc...",
    "operational_effect": "Enforcing descriptor-pinned dispatch converts the silent shadowing failure into a loud, attributable error at the exact call site, and it forces reload daemons to publish a new descriptor set rather than mutate the live one. The cost is one digest comparison per call and the need to re-plan when a digest changes mid-session (correct behavior: the plan is sta..."
  },
  "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": "4439b4cb7e9914c6dccba7771120db6c38dfc97455011205a3c307698d0f78d7",
    "verified_classes": [
      "DescriptorDriftError",
      "UnknownToolError",
      "PinnedRegistry"
    ],
    "verified_functions": [
      "_digest",
      "plan_tool_call",
      "__init__",
      "register",
      "dispatch"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "DescriptorDriftError",
      "UnknownToolError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "hashlib",
      "json",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
