{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-an-aaif-verifiable-credential-was-issued-under-a-stale-delegation-chain",
  "title": "What structural signals indicate an AAIF verifiable credential was issued under a stale delegation chain",
  "date_of_record": "2026 November 15",
  "scope": "This record applies to AAIF (Agent Authorization and Identity Framework) credential issuance where a root principal delegates authority through one or more intermediate agents before a leaf agent requests a verifiable credential (VC). It does not apply to single-hop issuance where the requesting agent holds authority directly from a human principal, nor to revocation propagation, which is a separate failure surface.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-aaif-verifiable-credential-was-issued-under-a-stale-delegation-chain.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-aaif-verifiable-credential-was-issued-under-a-stale-delegation-chain.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-aaif-verifiable-credential-was-issued-under-a-stale-delegation-chain.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1682,
    "python_slice_tokens": 175,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *chain validity at issuance time* and *chain validity at credential-use time*. AAIF requires that every VC embed the full delegation path — root principal → intermediate agent(s) → leaf agent — as a signed chain of `DelegationCredential` objects, each carrying a `not_after` timestamp, a `scope` set, and the issuing age...",
    "what_was_observed": "In a multi-tenant deployment, an orchestrator agent (`did:aaif:orch-7`) held a delegation from a tenant admin valid until 2026-11-14T18:00:00Z with scope `{read:orders, write:orders}`. The orchestrator issued short-lived sub-delegations to worker agents with a 4-hour `not_after`, refreshed hourly. A worker requested a VC for downstream batch processing with a requested TTL of 24 hours. The issuance service: 1. Verifi...",
    "condition_of_validity": "The invariant that *should* hold is: This is the **chain-lifetime ceiling**. It is valid whenever the credential embeds a multi-hop delegation path and the verifier is permitted (or required) to re-walk that path. It is *not* required when: - The credential is issued directly from a root principal (chain length 1), where `vc.exp <= root.not_after` is trivial...",
    "decision_boundary": "At issuance, compute `ceiling = min(link.not_after for link in chain)`. Then: - If `requested_exp <= ceiling`: mint with `exp = requested_exp`. Normal path. - If `requested_exp > ceiling`: **do not silently clamp and do not silently mint.** Clamping to `ceiling` produces a credential whose declared lifetime surprises the caller (batch jobs sized for 24h fail...",
    "operational_effect": "Enforcing the ceiling changes three things: 1. **Verifier determinism.** Every verifier in the trust domain, whether it re-walks the chain or not, reaches the same accept/reject decision for the entire declared lifetime of the credential. The split-brain disappears because the artifact never outlives its backing. 2. **Caller contract.** Callers learn that 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": "47a6960a990304eac306998910310e86e27f183e2e05853daa10b010791daaf3",
    "verified_classes": [
      "ChainLifetimeExceededError",
      "DelegationLink"
    ],
    "verified_functions": [
      "issue_credential",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ChainLifetimeExceededError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "datetime"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
