{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-skill-injection-detection-via-tool-manifest-signing-and-capability-diffing",
  "title": "What structural signals indicate skill-injection detection via tool manifest signing and capability diffing",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent runtimes that load tool/skill manifests from signed publishers and detect injected capabilities by diffing the declared capability set against a pinned baseline. Does not apply to unsigned manifests, to dynamic capability grants negotiated per-invocation, or to runtimes that execute tools out-of-process under a syscall sandbox where capability declaration is advisory only.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-skill-injection-detection-via-tool-manifest-signing-and-capability-diffing.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-skill-injection-detection-via-tool-manifest-signing-and-capability-diffing.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-skill-injection-detection-via-tool-manifest-signing-and-capability-diffing.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1416,
    "python_slice_tokens": 241,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Manifest signing proves *who declared* a capability set. Capability diffing proves *what changed* relative to a prior declaration. Neither proves *what the tool will actually do at runtime*. The non-obvious boundary failure is the assumption that these two checks compose into a safety invariant: that a valid signature over a manifest whose capability delta i...",
    "what_was_observed": "A publisher rotated a tool implementation from `v2.14.0` to `v2.14.1`. The manifest was re-signed with a valid publisher key. The declared capability list was byte-identical to the prior release: `[\"http:fetch\", \"fs:read:/data/inputs\", \"env:read:API_REGION\"]`. The capability differ, keyed on label strings, computed an empty delta and returned `SAFE_NO_CHANGE`. The runtime loaded the tool. The `v2.14.1` implementation...",
    "condition_of_validity": "The signing-plus-diffing invariant holds only when all of the following are true: 1. Each capability entry binds a label to a content digest of the implementing code path (or the whole artifact), and the diff operates on the `(label, impl_digest)` tuple set. 2. The signature covers the full tuple set including digests, so a re-signed manifest with a changed ...",
    "decision_boundary": "Treat an empty capability delta as *admissible* only when the manifest schema is tuple-addressed and the runtime enforces at the boundary. Treat it as *insufficient*—requiring manual review of the implementation diff—when: - The manifest is label-addressed (no `impl_digest` per capability). - The publisher rotated the signing key in the same release as the t...",
    "operational_effect": "Runtimes that gate on label-addressed diffs will admit implementation swaps under stable manifests at a rate proportional to publisher churn. The failure is silent and produces a clean audit trail—every check passed—which makes post-incident analysis harder, not easier, because the logs show `SAFE_NO_CHANGE` where a reviewer expects to find the anomaly. 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": "3671287810a3bc54ec2c3241df42c3b52286fda7287bc99244d52da3e88e46b0",
    "verified_classes": [
      "IndeterminateCapabilityDelta",
      "Capability"
    ],
    "verified_functions": [
      "diff_capabilities",
      "gate_manifest_load"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "IndeterminateCapabilityDelta"
    ],
    "sample_fail_closed_invariants": [
      "label-addressed manifest: empty delta cannot certify safety; require per-capability impl_digest before gating on diff re"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
