{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-halt-when-a-federated-agent-credential-chains-to-an-aaif-root-that-has-rotated-its-signing-key-mid-presentation",
  "title": "Where must an instance halt when a federated agent credential chains to an AAIF root that has rotated its signing key mid-presentation",
  "date_of_record": "2026 November 17",
  "scope": "Applies to relying parties (RPs) validating verifiable agent credentials (VACs) whose `issuer` DID resolves through an Authority-Anchored Identity Federation (AAIF) root, specifically when the presentation spans a root key rotation. Does not apply to credentials anchored to a single-org trust domain, nor to presentations where the entire chain is resolved within one atomic resolution window.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-halt-when-a-federated-agent-credential-chains-to-an-aaif-root-that-has-rotated-its-signing-key-mid-presentation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-halt-when-a-federated-agent-credential-chains-to-an-aaif-root-that-has-rotated-its-signing-key-mid-presentation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-halt-when-a-federated-agent-credential-chains-to-an-aaif-root-that-has-rotated-its-signing-key-mid-presentation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1386,
    "python_slice_tokens": 290,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **credential validity** and **chain continuity**. A VAC can be cryptographically valid at every individual link — issuer signature verifies, DID document resolves, root anchor is trusted — while the *chain itself* is discontinuous because the AAIF root rotated its signing key between the moment the credential was issue...",
    "what_was_observed": "During a cross-org federation between two AAIF members, an agent operating on behalf of Org A presented a VAC to Org B's resource gateway. The VAC was issued under Org A's intermediate DID, which chains to the AAIF root `did:aaif:root:prod`. The AAIF root had performed a scheduled key rotation 40 minutes prior. The credential's `issuanceDate` was 6 hours before presentation — comfortably within the credential's 24-ho...",
    "condition_of_validity": "A rotation-crossing chain is valid *if and only if* one of the following holds: 1. The credential's `issuanceDate` precedes the root key's `deactivated` timestamp **and** the credential's `expirationDate` precedes `deactivated + graceWindow`, where `graceWindow` is published in the AAIF root's `federationPolicy`. Both bounds must hold; issuance-before alone ...",
    "decision_boundary": "The boundary is not \"does the signature verify\" — it does. The boundary is: **does the RP have positive evidence that the authority under which the credential was issued was still authoritative at issuance time, and remains honored at presentation time?** If the RP cannot establish both halves from the chain material alone, it must halt and request re-attest...",
    "operational_effect": "RPs that fail to halt here exhibit two downstream pathologies. First, **silent grace-window extension**: every rotation-crossing credential is accepted regardless of age, because the deactivation timestamp is never compared to `expirationDate`. Over successive rotations, the effective trust window for cross-org agents grows without bound, and the AAIF root's..."
  },
  "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": "8e0e5d5b5348899e8812eff9f02b0f6620149178d6eaaca73f9cb346cf9fba20",
    "verified_classes": [
      "ChainIndeterminateError",
      "RootKeyState",
      "Credential"
    ],
    "verified_functions": [
      "validate_rotation_boundary",
      "handle_presentation"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ChainIndeterminateError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "datetime"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
