{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-delegated-capability-tokens-from-silently-widening-authority-across-cross-issuer-trust-chains",
  "title": "Which invariants prevent delegated capability tokens from silently widening authority across cross-issuer trust chains",
  "date_of_record": "2026 November 15",
  "scope": "Applies to AAIF-style delegated capability tokens where a resource-holder issues a token to an agent, which then re-delegates a narrowed subset to a sub-agent, and the verifier trusts more than one issuer (direct issuer plus one or more transitive trust anchors). Does not apply to single-issuer, non-delegated bearer tokens, nor to tokens whose authority set is fixed at issuance with no re-delegation path.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-delegated-capability-tokens-from-silently-widening-authority-across-cross-issuer-trust-chains.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-delegated-capability-tokens-from-silently-widening-authority-across-cross-issuer-trust-chains.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-delegated-capability-tokens-from-silently-widening-authority-across-cross-issuer-trust-chains.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1772,
    "python_slice_tokens": 376,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *attenuation* (the delegated token's authority set is a strict subset of the delegator's authority set, enforced at every hop) and *apparent attenuation* (the token *looks* narrower because the verifier only sees the leaf claims, but the union of claims along the chain is not actually checked for subset containment). C...",
    "what_was_observed": "A sub-agent presented a capability token whose leaf claims granted `read:orders` scoped to `tenant=42`. The leaf token was validly signed by the delegating agent, whose token was validly signed by the resource holder, whose token was signed by the trust anchor. Every signature verified. Every `exp` was in the future. Every `aud` matched. The verifier accepted the token. The leaf token also carried an `attenuation_pro...",
    "condition_of_validity": "The invariant holds only when all of the following are true simultaneously: 1. **Single-parent closure.** Every delegated token names exactly one parent, or names all parents and the verifier walks all of them. If the runtime can hold multiple parent tokens, the verifier must require a `parents: [hash, ...]` field and validate subset containment against the ...",
    "decision_boundary": "The operational decision is: **when the delegation graph is a DAG, reject any token whose parent set is not fully enumerated and fully validated, even if every reachable parent validates.** Do not fall back to \"validate the primary parent and trust the rest.\" The correct behavior on encountering an unenumerated parent is to fail closed with a distinct error,...",
    "operational_effect": "When the invariant is enforced, the operational effect is that delegation merges (an agent combining two capability tokens into one working context) require an explicit merge token that names both parents and whose authority set is the intersection of the parents' sets — not the union. This forces the merge to be a recorded, signed event rather than an impli..."
  },
  "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": "1388fbbc4e19e1a694f587c52ffd62b64ba505ff5087f763bd8fbd29ef32ce75",
    "verified_classes": [
      "DelegationGraphError",
      "CapabilityToken"
    ],
    "verified_functions": [
      "validate_chain",
      "merge_tokens"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "DelegationGraphError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
