{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-trusts-a-tool-manifest-s-declared-side-effect-class-after-registry-re-signing",
  "title": "What happens when an instance trusts a tool manifest's declared side-effect class after registry re-signing",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent runtimes that gate tool invocation on a manifest-declared side-effect classification (`read_only`, `mutating`, `external`) and that consume manifests from a plugin registry that permits re-signing or re-publication under the same skill identifier. Does not apply to runtimes that pin manifest digests out-of-band or that derive effect class from observed syscall/trace behavior rather than declaration.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-trusts-a-tool-manifest-s-declared-side-effect-class-after-registry-re-signing.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-trusts-a-tool-manifest-s-declared-side-effect-class-after-registry-re-signing.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-trusts-a-tool-manifest-s-declared-side-effect-class-after-registry-re-signing.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1310,
    "python_slice_tokens": 286,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A skill-injection attack is usually modeled as *content* poisoning: the skill's instructions or tool descriptions contain adversarial text that steers the model. The non-obvious boundary is different. Here the attacker never changes the model-visible text at all. They change the *manifest metadata* that the runtime uses to decide whether to sandbox, confirm,...",
    "what_was_observed": "A registry-hosted skill `web.fetch` declared `side_effects: read_only`. The runtime's policy engine, on seeing `read_only`, skipped the human-confirmation gate and routed the call through a permissive egress proxy that allowed arbitrary outbound POSTs (the proxy assumed read-only tools only issue GETs). A re-signed manifest for the same `web.fetch@1.4.2` changed the declared class to `read_only` **while** the tool sc...",
    "condition_of_validity": "The boundary holds only when all three of the following are true simultaneously: 1. The manifest's declared side-effect class is consumed by at least one *enforcement* decision (confirmation gate, network policy, filesystem scope), not merely by logging. 2. The registry permits re-publication or re-signing under a stable identifier without invalidating cache...",
    "decision_boundary": "Do not treat manifest signature validity as a proxy for side-effect-class correctness. The correct decision boundary is: - **Derive enforcement from schema, not declaration.** If a tool exposes `method`, `body`, `path`, `command`, or a free-form `args` parameter, its effective class is at least `mutating` regardless of the declared field. Compute `effective_...",
    "operational_effect": "After adopting schema-derived classification, the observed effect was a 100% catch rate on class-downgrade-plus-schema-widening revisions in replay, at the cost of a small false-positive rate: legitimate tools that add an optional `dry_run: bool` parameter were reclassified to `mutating` and began requiring confirmation. This is an acceptable trade — the fal..."
  },
  "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": "383b7ef4ebccb727482e7cc0f6f8f9aba5f28bd0d4abb81890f7112757e514b9",
    "verified_classes": [
      "ManifestPolicySkewError"
    ],
    "verified_functions": [
      "schema_implied_class",
      "effective_class",
      "approve_invocation",
      "__init__"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ManifestPolicySkewError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
