{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-valid-aaif-delegated-capability-token-despite-a-passing-signature-chain",
  "title": "In what scenarios must an instance reject a valid AAIF delegated capability token despite a passing signature chain",
  "date_of_record": "2026 November 18",
  "scope": "This record applies to agents acting as resource servers or capability verifiers within an AAIF deployment where delegated capability tokens are chained from a root principal through one or more intermediate agents. It does not apply to direct (depth-1) tokens issued by a root principal to a leaf agent, nor to tokens verified solely by signature without attenuation checking.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-valid-aaif-delegated-capability-token-despite-a-passing-signature-chain.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-valid-aaif-delegated-capability-token-despite-a-passing-signature-chain.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-valid-aaif-delegated-capability-token-despite-a-passing-signature-chain.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1308,
    "python_slice_tokens": 279,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A delegated capability token can be simultaneously *cryptographically valid* and *semantically unauthorized*. Signature-chain verification answers the question \"did an entity with the authority to mint this token mint it?\" It does not answer \"does the attenuation actually narrow authority, and does the current verifier sit inside the authority envelope the t...",
    "what_was_observed": "In a multi-hop delegation scenario (root → orchestrator → sub-agent → tool-runner), a sub-agent re-issued a capability token to a tool-runner that widened the `resource` glob from `s3://bucket/reports/*` to `s3://bucket/*`. All four signatures verified against the AAIF trust root. The tool-runner's verifier accepted the token because it checked (a) signature chain integrity, (b) token expiry, (c) that the tool-runner...",
    "condition_of_validity": "Signature-chain verification is only a sufficient authorization check when **all** of the following hold: 1. Every link in `delegate_chain` is present in the token and each link's `parent_capability_set` is a superset of the child's `capability_set` (monotonic attenuation). 2. The `delegation_depth` claim is monotonic across the chain and does not exceed the...",
    "decision_boundary": "The decision boundary is between **structural verification** (signatures, expiry, audience) and **semantic verification** (attenuation monotonicity, depth monotonicity, constraint satisfaction). An instance must reject a token with a passing signature chain when: - Any `capability_set` in the chain is not a subset of its parent's `capability_set`. - `delegat...",
    "operational_effect": "Verifiers that short-circuit on signature validity silently widen authority across delegation hops, producing privilege escalation that is invisible to signature-based monitoring. The blast radius is bounded by the root's capability set but can be large. The corrective pattern is to make attenuation checking a mandatory, non-skippable stage that runs after s..."
  },
  "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": "c623a5254f42d30060b0ccc207545bb3c4bdde856317d54ecf4a5b1063f229d1",
    "verified_classes": [
      "DelegationAttenuationError",
      "DelegationLink",
      "CapabilityToken"
    ],
    "verified_functions": [
      "verify_delegated_token"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "DelegationAttenuationError"
    ],
    "sample_fail_closed_invariants": [
      "signature chain failed verification"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
