{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-revoked-federated-agent-credential-propagated-across-an-aaif-trust-boundary",
  "title": "When must an instance refuse a revoked federated agent credential propagated across an AAIF trust boundary",
  "date_of_record": "2026 November 16",
  "scope": "Applies to federated agent identity systems where AAIF (Agent Authentication and Identity Federation) credentials are minted by a home organization and presented to relying parties in other trust domains, and where revocation is propagated asynchronously via revocation-list or push-notification channels. Does not apply to single-domain credential systems with synchronous revocation checks against a single authoritative store, nor to stateless bearer tokens whose lifetime is shorter than the revocation propagation window by design.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-revoked-federated-agent-credential-propagated-across-an-aaif-trust-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-revoked-federated-agent-credential-propagated-across-an-aaif-trust-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-revoked-federated-agent-credential-propagated-across-an-aaif-trust-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1798,
    "python_slice_tokens": 301,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **revocation propagation latency** and **credential rotation overlap**. Most federated agent implementations treat \"revoked\" and \"rotated\" as two points on the same lifecycle and collapse them into a single `valid`/`invalid` check. They are not the same invariant. A *rotation* is the home organization replacing a credentia...",
    "what_was_observed": "In a three-organization AAIF deployment (home issuer H, two relying parties R1 and R2), an agent credential was revoked at H at T+0 because the principal detected anomalous tool invocation. The revocation was published to H's revocation list with a `nextUpdate` of T+900s (15 minutes), matching the list's refresh cadence. R1, configured with a 60-second list refresh and a hard-fail-closed policy on list staleness, rej...",
    "condition_of_validity": "The rule \"honor a predecessor credential during the overlap window\" is valid **only if** the relying party can prove, at validation time, that the predecessor is in a rotation state and not a revocation state. In AAIF this proof requires one of: 1. A signed lifecycle assertion from H distinguishing `rotated` from `revoked`, delivered on the same channel and ...",
    "decision_boundary": "The decision procedure a relying party must execute on every presentation: - If the credential's `jti` appears on a freshly-fetched revocation list → reject, unconditionally. - If the list is stale beyond `maxStaleness` AND the credential's `notAfter` is in the future AND no synchronous introspection is available → **reject**. Do not apply grace. The princip...",
    "operational_effect": "After R2's grace policy was removed and replaced with hard-fail-closed on stale lists, R2's rejection rate during list-fetch failures rose from 0% to 100% of presentations during the failure window — a real availability cost. This was accepted because the alternative was an unbounded authorization gap whose width was `grace_window` and whose exploitability w..."
  },
  "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": "9533eb3ad31de09095d3dcf99dde9435c2a06f00a5c53b33f9ba73105829253a",
    "verified_classes": [
      "RevocationStateError"
    ],
    "verified_functions": [
      "validate_federated_credential"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "RevocationStateError"
    ],
    "sample_fail_closed_invariants": [
      "credential missing jti; cannot resolve revocation state"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
