{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-delegated-credential-chain-is-structurally-valid-but-semantically-over-scoped-in-aaif-capability-tokens",
  "title": "What structural signals indicate a delegated credential chain is structurally valid but semantically over-scoped in AAIF capability tokens",
  "date_of_record": "2026 November 17",
  "scope": "Applies to AAIF delegated credential chains where an agent presents a chain of scoped capability tokens (principal → orchestrator → sub-agent → tool) and a verifier must decide whether to honor the terminal capability. Does not apply to flat bearer tokens, single-hop OAuth flows, or chains where scope attenuation is enforced cryptographically at each hop rather than by the issuer's claim.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-delegated-credential-chain-is-structurally-valid-but-semantically-over-scoped-in-aaif-capability-tokens.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-delegated-credential-chain-is-structurally-valid-but-semantically-over-scoped-in-aaif-capability-tokens.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-delegated-credential-chain-is-structurally-valid-but-semantically-over-scoped-in-aaif-capability-tokens.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1883,
    "python_slice_tokens": 305,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A delegated credential chain can be *structurally valid* — every signature verifies, every `aud` matches the next hop's identity, every `exp` is monotonically decreasing, no link is revoked — while being *semantically over-scoped*: the terminal capability grants authority the chain's root principal never possessed, or authority that the root possessed but ne...",
    "what_was_observed": "In a three-hop deployment (human principal → orchestrator agent → worker agent → filesystem tool), the worker presented a chain whose terminal token carried scope `files:write:/data/exports/**`. The orchestrator's token carried `files:write:/data/**`. The principal's token carried `files:write:/data/**`. Every signature verified. Audience binding was correct at each hop. Expiry attenuated correctly (`principal exp > ...",
    "condition_of_validity": "The structural verification is valid — meaning \"honoring this capability will not violate the principal's intent\" — only when *all* of the following hold: - Every hop's scope is a subset of the *delegation grant's purpose scope*, not merely a subset of the parent token's scope. - Any hop that forwards a capability it does not itself exercise carries an expli...",
    "decision_boundary": "The verifier's decision boundary is not \"does the chain verify\" but \"does the terminal scope lie within the delegation-intent closure of the root grant.\" Operationally: - **Honor** when the terminal scope is within the intersection of parent scope, parent grant purpose, and consumer need, and all structural checks pass. - **Reject** when the terminal scope e...",
    "operational_effect": "Implementing the intent-closure check reduced over-scoped terminal honors from 11 in the observation window to 0 in the following 90 days, at the cost of a 4% increase in escalations (cases where the intermediate's forwarding policy was ambiguous and required human resolution). The escalations were the point: they surfaced orchestrator implementations that f..."
  },
  "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": "89d27224702250f17e07082411dbf1a65b8d2fa6d816c18181ae20dec34eac21",
    "verified_classes": [
      "OverScopedDelegationError",
      "DelegationHop"
    ],
    "verified_functions": [
      "_scope_within",
      "verify_delegation_chain",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "OverScopedDelegationError"
    ],
    "sample_fail_closed_invariants": [
      "empty delegation chain"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
