{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-presents-an-aaif-credential-whose-aud-matches-the-verifier-but-whose-delegated-scope-was-issued-against-a-stale-parent-c",
  "title": "What happens when an instance presents an AAIF credential whose `aud` matches the verifier but whose delegated `scope` was issued against a stale parent chain",
  "date_of_record": "2026 November 17",
  "scope": "Applies to AAIF credential verification where a leaf agent credential is presented to a resource server that validates `aud`, signature, and expiry but does not re-resolve the full delegation chain to the root issuer at verification time. Does not apply to single-hop credentials with no `act` (actor) claim, nor to deployments enforcing online introspection against the issuer on every request.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-an-aaif-credential-whose-aud-matches-the-verifier-but-whose-delegated-scope-was-issued-against-a-stale-parent-c.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-an-aaif-credential-whose-aud-matches-the-verifier-but-whose-delegated-scope-was-issued-against-a-stale-parent-c.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-an-aaif-credential-whose-aud-matches-the-verifier-but-whose-delegated-scope-was-issued-against-a-stale-parent-c.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1313,
    "python_slice_tokens": 116,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *audience validity* and *delegation-chain validity*. An AAIF credential carries two independent authorization facts: (1) the `aud` claim binding the credential to a specific verifier, and (2) the `act`/`scope` chain recording which principal delegated which subset of authority down to the presenting instance. Verifiers...",
    "what_was_observed": "In a multi-tenant agent mesh, a planner agent delegated `data:read` and `data:export` to a worker agent via a two-hop AAIF chain. The worker's credential had `aud: \"export-service\"` and verified cleanly. Roughly forty minutes later, the planner's own parent credential was re-issued with `data:export` removed (a policy tightening pushed by the tenant). The worker's leaf credential was *not* re-issued — AAIF does not m...",
    "condition_of_validity": "The `aud`-only verification path is valid **if and only if** one of the following holds: - The delegation chain is single-hop (leaf issued directly by root, no `act` chain), so there is no intermediate authority that can drift. - The issuer guarantees cascading re-issuance: any parent scope change forces immediate re-issuance or revocation of all descendants...",
    "decision_boundary": "The operational decision is where to place the cost of chain re-resolution. Three viable positions: 1. **Verify-time resolution.** Walk the `act` chain to the root on every request. Correct, but adds a root lookup to the hot path and requires the root to be reachable — unacceptable for cross-domain or offline-tolerant deployments. 2. **Bounded-staleness acce...",
    "operational_effect": "Deployments that adopt the `iat`-ordering check see a small uptick in rejected credentials immediately after any parent re-issuance — these are the stale leaves, correctly refused. The effect is that scope narrowing propagates at the speed of the next leaf presentation rather than at the speed of the leaf's TTL. The cost is that well-behaved workers must re-..."
  },
  "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": "33b786190822974563fb0a205b9af8634737ebf8c12dcb0333b206804e947bfc",
    "verified_classes": [
      "StaleDelegationChainError"
    ],
    "verified_functions": [
      "verify_aaif_leaf"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "StaleDelegationChainError"
    ],
    "sample_fail_closed_invariants": [
      "leaf credential expired"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
