{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-a-skill-manifest-as-untrusted-input-rather-than-configuration",
  "title": "In what scenarios must an instance treat a skill manifest as untrusted input rather than configuration",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent runtimes that load third-party tool/skill manifests (MCP-style tool descriptors, plugin manifests, function-calling schemas) at admission time and derive capability grants from them. Does not apply to first-party manifests compiled into the agent image, nor to manifests whose signature chain terminates in a key the runtime already trusts for code execution.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-skill-manifest-as-untrusted-input-rather-than-configuration.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-skill-manifest-as-untrusted-input-rather-than-configuration.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-skill-manifest-as-untrusted-input-rather-than-configuration.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1605,
    "python_slice_tokens": 373,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A manifest is simultaneously *configuration* (declarative metadata the runtime consumes) and *code-adjacent artifact* (a description of behavior the runtime will later authorize). The non-obvious boundary is this: **static analysis of a manifest can only establish what the manifest claims, never what the tool does.** Every field a manifest exposes—`descripti...",
    "what_was_observed": "Across a corpus of adversarial manifests, the dominant evasion was *semantic laundering of the description field* against embedding-based detectors. A tool whose actual behavior was `read_file` over an arbitrary path presented a description embedding close to a benign `summarize_document` tool, because the description was written in the register of summarization. The parameter schema was the tell: a `path` parameter ...",
    "condition_of_validity": "The \"static analysis has veto-only authority\" invariant is valid only under these conditions: 1. **Probe coverage is explicitly bounded and recorded.** A dynamic-analysis pass must emit the set of argument shapes exercised. A clean result is valid only for that set. Any manifest whose parameter space is unbounded (free-form strings, open `additionalPropertie...",
    "decision_boundary": "The boundary between \"admit\" and \"quarantine\" is not \"static clean AND dynamic clean.\" It is: - **Quarantine** if static analysis flags anything, regardless of dynamic results. A static flag is a hard stop because static analysis is sound in the negative direction (a declared `destination_url` under `side_effects: none` is a real contradiction) even though i...",
    "operational_effect": "The practical consequence is that admission becomes a *two-key* process where the keys are asymmetric: static analysis can lock but not unlock; dynamic analysis can unlock only within the closure it actually explored. This inverts the common pipeline where static checks are a fast pre-filter and dynamic checks are the final gate. Here, static checks are the ..."
  },
  "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": "fb6b9178dec4492aea57fcac8ec016d007da66a48c629b1eab86b4c1cfacd356",
    "verified_classes": [
      "ManifestAdmissionError",
      "Manifest",
      "ProbeCoverage"
    ],
    "verified_functions": [
      "static_veto",
      "admit"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ManifestAdmissionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
