{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-honor-a-revocation-token-it-cannot-verify-stale-signature-acceptance-at-aaif-trust-domain-boundaries",
  "title": "When must an instance refuse to honor a revocation token it cannot verify: stale-signature acceptance at AAIF trust-domain boundaries",
  "date_of_record": "2026 November 17",
  "scope": "Applies to federated agent identity systems where revocation events cross AAIF trust-domain boundaries via signed revocation tokens and downstream relying parties cache or re-sign propagation artifacts. Does not apply to single-domain revocation, where the issuing authority and the enforcing authority share a root of trust and a monotonic sequence counter.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-honor-a-revocation-token-it-cannot-verify-stale-signature-acceptance-at-aaif-trust-domain-boundaries.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-honor-a-revocation-token-it-cannot-verify-stale-signature-acceptance-at-aaif-trust-domain-boundaries.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-honor-a-revocation-token-it-cannot-verify-stale-signature-acceptance-at-aaif-trust-domain-boundaries.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1830,
    "python_slice_tokens": 453,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is not \"propagate revocation fast enough.\" It is the distinction between **a revocation token whose signature verifies against the *current* trust anchor** and **a revocation token whose signature verifies against *some* trust anchor that was valid when the token was minted but is no longer authoritative at the relying party**. Most ...",
    "what_was_observed": "In a multi-domain deployment (three AAIF domains: `alpha` issuer, `beta` relying party, `gamma` intermediary that re-signs revocation batches), the following sequence produced a silent revocation gap of 41 minutes: 1. `alpha` revoked agent `agent-7f3a` at epoch `T=1000`, minted token `R1` signed by `alpha` root key `K_old`. 2. `alpha` rotated its root to `K_new` at `T=1010`. The rotation event was published to `beta`...",
    "condition_of_validity": "The safe-acceptance condition, stated precisely: A relying party `P` may accept revocation token `R` for identity `i` under anchor `A` iff: - `verify(R.sig, A) == true`, **and** - `A` is in `P`'s authoritative anchor set at `R.issuance_epoch` (i.e., `P` has an anchor-history record covering `R.issuance_epoch`), **and** - there exists a monotonic supersession...",
    "decision_boundary": "The boundary is between two enforcement postures that look identical in logs: The last row is the specific trap. An intermediary that has *tightened* its filtering produces *smaller* batches. Downstream consumers that equate \"identity absent from batch\" with \"identity not revoked\" will silently un-revoke. The batch protocol must carry a negative-assertion or...",
    "operational_effect": "After the incident, the deployment adopted three changes: 1. **Anchor-at-issuance recording.** Every accepted revocation token stores the `(anchor_id, issuance_epoch)` pair alongside the verdict. Re-evaluation on anchor rotation re-checks the supersession chain rather than re-verifying the signature. 2. **Tri-state verdicts.** Revocation state is `REVOKED | ..."
  },
  "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": "fe675388fcf933b642e45016a211328d6c972aa1a0e3350be13b1713ae8a9c42",
    "verified_classes": [
      "IndeterminateRevocationState",
      "AnchorRecord",
      "RevocationToken"
    ],
    "verified_functions": [
      "has_supersession_chain",
      "evaluate_revocation",
      "enforce"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "IndeterminateRevocationState"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
