{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-delegated-aaif-credential-chain-despite-a-valid-signature-at-every-hop",
  "title": "In what scenarios must an instance reject a delegated AAIF credential chain despite a valid signature at every hop",
  "date_of_record": "2026 November 15",
  "scope": "Applies to AAIF v1.x delegated credential chains where each hop carries a verifiable signature (JWS or COSE) and the verifier is validating a request on behalf of a leaf agent. Does not apply to first-party (non-delegated) credentials, nor to single-hop tokens where the issuer is also the resource owner.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-delegated-aaif-credential-chain-despite-a-valid-signature-at-every-hop.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-delegated-aaif-credential-chain-despite-a-valid-signature-at-every-hop.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-delegated-aaif-credential-chain-despite-a-valid-signature-at-every-hop.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1386,
    "python_slice_tokens": 271,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Signature validity is a per-link property; authorization validity is a path property. A chain can be cryptographically intact at every hop while being operationally invalid because the *composition* of delegations violates an invariant that no individual hop can detect in isolation. The non-obvious failure is this: **a delegation may be signed by a principal...",
    "what_was_observed": "During interoperability testing between two AAIF-conformant runtimes (call them A and B), a chain of length three was constructed: - Root principal `P0` issues to agent `A1` a credential scoped to `{read:orders, write:orders}` with `may_delegate=true` restricted to `read:orders`. - `A1` delegates to `A2` a credential scoped to `{read:orders, write:orders}` — signing a *superset* of what `P0` permitted it to delegate....",
    "condition_of_validity": "A delegated AAIF chain is valid for a request iff **all** of the following hold, evaluated over the full path from root to leaf: 1. Every hop signature verifies against the issuer's key *at the epoch named in that hop*. 2. For every hop `i` with issuer `I_i` delegating to `I_{i+1}`: `scope(I_{i+1}) ⊆ delegated_scope(I_i)`, where `delegated_scope(I_i)` is the...",
    "decision_boundary": "The operational rule: **a verifier must reject the chain when any hop's declared scope is not a subset of the delegable scope its issuer actually held — even if the leaf's scope is a subset of every declared scope on the path.** Do not accept on the basis of \"leaf ⊆ parent\" alone. Walk the path, carrying a running `permitted` intersection, and reject the mom...",
    "operational_effect": "Implementations that check only pairwise subsets (Runtime A above) will accept over-broad intermediate credentials, creating latent privilege that a compromised intermediate agent can exercise without ever touching the leaf. The observable symptom is not a failed signature but an *authorization grant that no single log line explains*: an audit trail where ev..."
  },
  "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": "ef76642dbc6502c0c6e311e4e1abeecbc80b2066612dd95d2d36305f7933c207",
    "verified_classes": [
      "DelegationScopeViolation",
      "EpochSuperseded"
    ],
    "verified_functions": [
      "verify_chain"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "DelegationScopeViolation",
      "EpochSuperseded"
    ],
    "sample_fail_closed_invariants": [
      "empty delegation chain"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
