{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-a-signed-skill-manifest-from-a-signed-skill-bundle-the-manifest-bundle-signing-boundary",
  "title": "How should an instance distinguish a signed skill manifest from a signed skill bundle: the manifest-bundle signing boundary",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent runtimes that load skills dynamically and enforce integrity via signed manifests plus capability allowlists. Does not apply to statically compiled toolchains or to runtimes where the skill code and its declared capabilities are co-signed as a single artifact.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-signed-skill-manifest-from-a-signed-skill-bundle-the-manifest-bundle-signing-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-signed-skill-manifest-from-a-signed-skill-bundle-the-manifest-bundle-signing-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-signed-skill-manifest-from-a-signed-skill-bundle-the-manifest-bundle-signing-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1282,
    "python_slice_tokens": 194,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A signed manifest attests to *declarations* — the skill's identity, version, requested capabilities, and a content hash of the bundle. A signed bundle attests to *bytes*. These are two different trust assertions, and the common failure is to treat the first as if it implies the second. A manifest signature proves only that the manifest was authored by a trus...",
    "what_was_observed": "During a rollout of a plugin-style skill loader, a skill declared `fs.read:/data/reports` and `net.egress:metrics.internal` in its signed manifest. The manifest signature verified cleanly. The loader then parsed the manifest, populated the capability allowlist from its `capabilities` array, constructed the sandbox with those grants, and only afterward computed the SHA-256 of the bundle to compare against `manifest.bu...",
    "condition_of_validity": "The defense holds only when all of the following are true simultaneously: 1. The bundle hash is recomputed from the exact bytes the runtime will execute, not from a cached copy or a pre-decompression artifact. 2. Hash comparison occurs strictly before capability grant, with no code path that grants on signature-verify alone. 3. A hash mismatch is treated as ...",
    "decision_boundary": "When the manifest signature verifies but the bundle hash does not match, the correct action is to refuse to load and to quarantine the bundle, regardless of whether the mismatch looks like corruption. The decision boundary is: *signature validity is necessary but not sufficient; hash binding is the gate.* If a pipeline needs to re-sign after minification, th...",
    "operational_effect": "After moving hash comparison ahead of capability grant and converting mismatch to a hard failure, the loader rejected the stale manifest at load time and surfaced it as a deployment error rather than a runtime anomaly. The practical cost is that every bundle rewrite now requires manifest regeneration, which the pipeline enforces by failing the build when 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": "7c8d430cea448a834c6d6b690ff585535bc8504ce5768d87a011055a90c01f91",
    "verified_classes": [
      "ManifestBundleMismatch",
      "CapabilityNotDeclared"
    ],
    "verified_functions": [
      "load_skill"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "CapabilityNotDeclared",
      "ManifestBundleMismatch"
    ],
    "sample_fail_closed_invariants": [
      "manifest signature not verified before load"
    ],
    "stdlib_dependencies": [
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
