{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-delegated-agent-credential-has-silently-outlived-its-authorization-scope",
  "title": "What structural signals indicate a delegated agent credential has silently outlived its authorization scope",
  "date_of_record": "2026 November 17",
  "scope": "Applies to AAIF delegated credentials (agent-to-agent and agent-to-tool) where scope is expressed as a capability set plus a delegation chain, and where revocation is propagated via a directory or CRL-like channel rather than per-request introspection. Does not apply to short-lived bearer tokens whose validity is bounded by a single TTL and verified synchronously on every call.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-delegated-agent-credential-has-silently-outlived-its-authorization-scope.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-delegated-agent-credential-has-silently-outlived-its-authorization-scope.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-delegated-agent-credential-has-silently-outlived-its-authorization-scope.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1718,
    "python_slice_tokens": 469,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"credential is revoked but still accepted.\" That is a propagation-latency problem, observable by monitoring revocation-to-enforcement lag. The non-obvious boundary is subtler: a delegated credential can remain *structurally valid* — signature chain intact, not expired, not on any revocation list — while the *authorization it encodes* ...",
    "what_was_observed": "Over a multi-week observation window across three agent fleets, the following structural signals preceded incidents where a delegated agent exercised authority its root principal no longer held: 1. **Chain-root divergence without signature failure.** The credential's `delegator_id` at depth 0 still resolved to a principal whose capability set no longer contained the delegated scope, yet every signature in the chain v...",
    "condition_of_validity": "The invariant that actually holds is narrow: > A delegated credential is authorized at time *t* **iff** every principal in its chain holds, at time *t*, the capability the leaf asserts — not merely that each held it at mint time. This invariant is *not* enforced by signature verification, expiry checks, or leaf-keyed revocation. It is enforced only if the ve...",
    "decision_boundary": "The decision boundary for an operator or agent runtime: - **If** your verifier does leaf-keyed revocation lookup and signature-chain validation only, **then** you are exposed to orphaned-credential over-privilege whenever a delegator is narrowed. Treat every delegated credential's effective scope as `min(leaf_scope, current_scope_of_each_ancestor)` and compu...",
    "operational_effect": "The practical consequence is that AAIF delegated credentials behave as *capability leases*, not capability grants. A lease's terms are re-read at exercise time. Systems that model them as grants accumulate silent over-privilege proportional to delegation depth and inversely proportional to leaf TTL. The mitigation is structural: key revocation by principal, ..."
  },
  "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": "c488cfbf6e6e2d0603b64651144d61386f1219653302821aaaabcb89fe8bcc01",
    "verified_classes": [
      "OrphanedDelegationError",
      "DelegatedCredential",
      "Principal"
    ],
    "verified_functions": [
      "evaluate_delegation",
      "authorize_action"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 8,
    "raised_exceptions": [
      "OrphanedDelegationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
