{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-re-verify-a-delegated-credential-chain-when-per-tool-scoped-tokens-cross-an-authorization-scope-boundary",
  "title": "Where must an instance re-verify a delegated credential chain when per-tool scoped tokens cross an authorization scope boundary",
  "date_of_record": "2026 November 17",
  "scope": "Applies to AAIF-style delegated credential chains where an agent instance presents a per-tool scoped token derived from a parent delegation, and the request crosses a scope boundary (tool, resource namespace, or audience). Does not apply to single-hop, non-delegated bearer tokens or to chains where every hop shares one flat scope set.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-re-verify-a-delegated-credential-chain-when-per-tool-scoped-tokens-cross-an-authorization-scope-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-re-verify-a-delegated-credential-chain-when-per-tool-scoped-tokens-cross-an-authorization-scope-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-re-verify-a-delegated-credential-chain-when-per-tool-scoped-tokens-cross-an-authorization-scope-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1578,
    "python_slice_tokens": 279,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct questions in a delegated credential chain, and conflating them is the root of the failure mode: 1. **Chain validity** — is every signature in the delegation chain intact, unexpired, and rooted in a trusted issuer? 2. **Scope containment** — is the *effective* permission of the leaf token a subset of every ancestor's granted scope, alon...",
    "what_was_observed": "An agent instance `A` held a delegation chain: root principal `P` → orchestrator `O` (scope: `repo:read`, `repo:write`, `db:read`) → worker `W` (scope: `repo:read`, `db:read`). `W` requested a per-tool token for `db.read` scoped to `db://prod/analytics`. The edge validated the chain signatures, confirmed `db:read` was present in `W`'s scope, and issued the leaf token. The tool executed a query against `db://prod/anal...",
    "condition_of_validity": "The invariant that must hold at every scope boundary: > For a request `r` (tool `t`, resource `R`, audience `aud`) presented with leaf token `L` and chain `P → … → L`, authorization holds **iff** for every ancestor `a` in the chain, `scope(a)` contains `(t, R, aud)` **as of the evaluation time**, and `L` was minted on a delegation path whose ancestors are ex...",
    "decision_boundary": "Re-verify the full chain-against-current-ancestor-scope at the boundary when **any** of the following is true: - The requested tool differs from the tool the cached evaluation was computed for. - The requested resource is outside the resource namespace of the cached evaluation. - The requested audience differs from the token's bound audience. - The leaf toke...",
    "operational_effect": "The practical consequence is that per-tool scoped tokens must be treated as **attenuated claims requiring boundary re-validation**, not as bearer capabilities. Systems that cache chain validity at the edge and trust the leaf token will, under temporal attenuation or sibling-branch delegation, execute requests that no ancestor currently authorizes. The failur..."
  },
  "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": "8aff0db23caa4d33d4016031f8fd0e4945ffe9fed174aa96fe6e4c3bbb8754ed",
    "verified_classes": [
      "DelegationScopeViolation",
      "Scope",
      "Ancestor",
      "LeafToken"
    ],
    "verified_functions": [
      "verify_at_boundary",
      "contains"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "DelegationScopeViolation"
    ],
    "sample_fail_closed_invariants": [
      "empty delegation chain; no root to anchor trust"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
