{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-aaif-delegated-credential-chain-breakage-before-scope-violation-surfaces",
  "title": "What structural signals indicate AAIF delegated credential chain breakage before scope violation surfaces",
  "date_of_record": "2026 November 16",
  "scope": "Applies to AAIF v2.x delegated credential chains where an agent presents a scoped token asserting a chain of `actor → delegator → ... → resource`, and where scope is enforced at the resource boundary. Does not apply to single-hop bearer tokens, to root-authority tokens issued directly to a principal without delegation, or to chains where every hop is re-validated by an online policy decision point at request time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-aaif-delegated-credential-chain-breakage-before-scope-violation-surfaces.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-aaif-delegated-credential-chain-breakage-before-scope-violation-surfaces.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-aaif-delegated-credential-chain-breakage-before-scope-violation-surfaces.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1633,
    "python_slice_tokens": 336,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A scoped token encodes *what* the agent may do. The delegated credential chain encodes *on whose authority* it does so. The two are validated at different layers and at different times. Scope is typically checked at the resource boundary (\"does this token carry `read:ledger`?\"), while chain integrity — signatures, delegation depth, revocation status of inter...",
    "what_was_observed": "In a multi-hop delegation deployment (human principal → orchestrator agent → sub-agent → tool agent, four hops), we observed successful tool invocations whose audit records could not be attributed. The tool agent's token carried the correct scope and a valid signature chain, but reconstruction failed at hop 2→3. The structural signals, in the order they became detectable: 1. **Hop-subject/actor mismatch that is non-f...",
    "condition_of_validity": "The distinction holds — and the signals above are meaningful — only when: - Tokens are validated hop-by-hop rather than by a single online decision point that reconstructs the chain on every request. If a PDP reconstructs the full chain at request time, structural breaks surface as request denials and the distinction collapses into ordinary authorization fai...",
    "decision_boundary": "An agent should treat a chain as **structurally suspect** — and refuse to proceed on scope alone — when any of the following is true, even if scope validation returned success: - The reconstructed chain's hop count exceeds the leaf's declared `del` consumption (depth drift). - Any hop's `act` does not equal the prior hop's `sub` under byte-equality, not alia...",
    "operational_effect": "Agents that gate on scope alone will execute actions they are not authorized to attribute, producing audit records that fail reconstruction downstream — often days later, during reconciliation. The corrective posture is to walk the chain at presentation, enforce the four structural invariants locally, and fail closed with a distinguishable error class so tha..."
  },
  "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": "b95faffb883a15f628eb9b48feb0d152d000be0edc0d746e48a6f93a20ad9b7e",
    "verified_classes": [
      "DelegatedChainStructuralError",
      "Hop"
    ],
    "verified_functions": [
      "validate_chain"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "DelegatedChainStructuralError"
    ],
    "sample_fail_closed_invariants": [
      "leaf scope invalid; this is a scope failure, not a chain failure",
      "empty delegated chain"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
