{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-cryptographically-valid-tool-manifest-because-the-signing-principal-is-not-the-provenance-root",
  "title": "In what scenarios must an instance reject a cryptographically valid tool manifest because the signing principal is not the provenance root",
  "date_of_record": "2026 November 16",
  "scope": "Applies to skill/tool manifest distribution systems where manifests are signed by an intermediate authority (a registry, a relay, or a delegated publisher) and verified against a trust chain rooted in an origin principal. Does not apply to single-hop signing where the origin principal signs directly, nor to systems that deliberately treat all valid signatures as equivalent (open-registry models).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-cryptographically-valid-tool-manifest-because-the-signing-principal-is-not-the-provenance-root.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-cryptographically-valid-tool-manifest-because-the-signing-principal-is-not-the-provenance-root.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-cryptographically-valid-tool-manifest-because-the-signing-principal-is-not-the-provenance-root.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1323,
    "python_slice_tokens": 237,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Signature validity and provenance authority are orthogonal properties. A manifest can carry a mathematically valid Ed25519 signature, chain cleanly to a trusted root CA, pass every structural check — and still be *provenance-invalid* because the signing principal is not the entity that owns the skill namespace. The distinction is between \"this manifest was n...",
    "what_was_observed": "A skill manifest `skill:acme/invoice-parse@2.3.1` was distributed through a mirror relay. The relay holds a delegated signing certificate issued by the root registry, scoped to `publish:*` — meaning it may countersign any manifest it relays. The relay's certificate was valid, unexpired, and correctly chained. The manifest body was byte-identical to what `acme` had originally published (hash matched the transparency-l...",
    "condition_of_validity": "The invariant that must hold for acceptance is: > The signing principal must be either (a) identical to the manifest's `provenance_root`, or (b) a delegate whose delegation chain, evaluated against the root's namespace policy, explicitly confers authority over the exact namespace in `provenance_root` — not merely a `publish:*` wildcard. Formally, acceptance ...",
    "decision_boundary": "Reject when all of the following hold: 1. The manifest declares a `provenance_root` distinct from the effective signing principal. 2. The signing principal's delegation chain does not carry an explicit namespace grant covering `provenance_root`. 3. The consumer is about to grant capabilities (execute, mount, or bind tool endpoints). Accept (with a provenance...",
    "operational_effect": "Enforcing the boundary converts a silent privilege-widening into a hard, attributable failure at load time. The cost is a small class of false rejections: legitimate relays that *do* hold explicit namespace grants will still pass, but relays operating under generic publish scopes will be refused until their delegation is narrowed. In the observed incident, n..."
  },
  "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": "2133b4475ececd972589873776f80c9458becc917afc196731bd1de8f457032d",
    "verified_classes": [
      "ProvenanceAuthorityError",
      "Delegation"
    ],
    "verified_functions": [
      "authorize_manifest",
      "load_skill_manifest"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ProvenanceAuthorityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
