{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-handle-delegated-scope-attenuation-when-a-capability-token-s-subject-chain-crosses-a-workload-identity-re-mint-boundary",
  "title": "How should an instance handle delegated-scope attenuation when a capability token’s subject chain crosses a workload-identity re-mint boundary",
  "date_of_record": "2026 November 16",
  "scope": "Applies to AAIF deployments where per-tool capability tokens are minted against a workload identity (WI) and carry a delegated-scope chain derived from an upstream principal. Does not apply to static service-account tokens with no delegation chain, nor to tokens whose subject is a human principal directly authenticated at the tool boundary.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-handle-delegated-scope-attenuation-when-a-capability-token-s-subject-chain-crosses-a-workload-identity-re-mint-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-handle-delegated-scope-attenuation-when-a-capability-token-s-subject-chain-crosses-a-workload-identity-re-mint-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-handle-delegated-scope-attenuation-when-a-capability-token-s-subject-chain-crosses-a-workload-identity-re-mint-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1659,
    "python_slice_tokens": 226,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *scope attenuation* (the monotonic narrowing of permissions as delegation descends) and *identity continuity* (the guarantee that the subject named in a capability token is the same workload that is presenting it). These two invariants are enforced by different subsystems — the delegation engine narrows scopes; the workloa...",
    "what_was_observed": "In a multi-tenant tool-calling deployment, a planner agent delegated a `read:dataset` scope to a worker workload, which minted a per-tool capability token for a database tool. The worker pod was rescheduled during a rolling node drain. On re-mint: 1. The new WI credential was issued with a fresh epoch `e2`; the old epoch `e1` credential was revoked. 2. The capability token, still within its TTL, presented successfull...",
    "condition_of_validity": "The invariant “a capability token’s delegated scope is bound to the WI epoch under which it was minted” holds only when all of the following are true: - The capability token embeds an explicit, signed subject-epoch reference, not merely a subject name. - The authorization decision compares the embedded epoch to the live WI epoch, and treats a mismatch as a *...",
    "decision_boundary": "The operational decision is whether a stale-epoch capability token should be **rejected** or **re-anchored** at the tool boundary: - **Reject** when the re-mint crossed an attestation-class boundary (different node pool, different measurement, different trust tier). The scope was delegated against specific evidence; a different evidence basis must not inheri...",
    "operational_effect": "Enforcing epoch-equality converts a silent scope-continuity break into an explicit, countable denial at the re-mint boundary. The operational consequences are: - A burst of `StaleEpochDelegation` denials correlated with node drains and SVID rotations — expected and benign if the re-delegation path is healthy. - Re-delegation latency added to the first tool c..."
  },
  "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": "9998727cbc7799454b887df4836a401c93a09b564cf045b3ba5fa2a377d92f9e",
    "verified_classes": [
      "StaleEpochDelegation",
      "CapabilityToken",
      "LiveWorkloadIdentity"
    ],
    "verified_functions": [
      "authorize_tool_call"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "StaleEpochDelegation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
