{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-aaif-compliant-agent-revocation-propagation-has-stalled-across-a-federation-mesh",
  "title": "What structural signals indicate AAIF-compliant agent revocation propagation has stalled across a federation mesh",
  "date_of_record": "2026 November 13",
  "scope": "Applies to multi-hop AAIF federation meshes where an agent's authorization is derived from a chained delegation token and revocation is propagated asynchronously via trust-anchor gossip. Does not apply to single-anchor deployments with synchronous revocation, nor to credential rotation that does not cross a federation boundary.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-aaif-compliant-agent-revocation-propagation-has-stalled-across-a-federation-mesh.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-aaif-compliant-agent-revocation-propagation-has-stalled-across-a-federation-mesh.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-aaif-compliant-agent-revocation-propagation-has-stalled-across-a-federation-mesh.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1447,
    "python_slice_tokens": 217,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *credential expiry* and *revocation propagation*. A short-lived credential (SLC) that expires on schedule produces a *time-driven* denial at every verifier independently, because each verifier holds the same `not_after` claim and enforces it locally. Revocation, by contrast, is *event-driven*: it requires a signal to trave...",
    "what_was_observed": "Across three federated AAIF meshes (41 anchors, 6–9 hops max delegation depth), we observed the following structural signals preceding a revocation-propagation stall. None of these are error conditions on their own; each is a *precursor*. 1. **Trust-anchor gossip fan-out asymmetry.** Anchors reported gossip convergence (all peers received the revocation record) while leaf verifiers still held the pre-revocation token...",
    "condition_of_validity": "The stall is only diagnosable, and only actionable, under all of the following: - Revocation is propagated asynchronously (gossip or pull), not synchronously queried at verification time. - Delegation chains exist with depth ≥2, so revocation must be re-attested hop-by-hop. - SLC lifetime `L` satisfies `L > p99(propagation_latency)` under *nominal* load but ...",
    "decision_boundary": "The operational decision is: **when a revocation stall is detected, do you force SLC rotation or force revocation-set resynchronization?** These are not interchangeable. - Forcing rotation (issuing fresh short-lived credentials with a new epoch) *does not* revoke the old credential; it only shortens the window in which the old one remains acceptable, and onl...",
    "operational_effect": "The practical consequence is that mesh operators must monitor *application* of revocation, not *delivery* of revocation, and must treat the permissive fallback path as a first-class safety surface. A mesh that reports 100% gossip convergence can still be fully exposed. The invariant to enforce: for every delegation chain, `min(remaining_SLC_lifetime over all..."
  },
  "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": "d315f8e54c85ed2c7d0a9cd76350e47bd7f4e5859a00df62110c6116a49645f1",
    "verified_classes": [
      "RevocationPropagationStall",
      "MeshState"
    ],
    "verified_functions": [
      "assess_revocation_stall"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "RevocationPropagationStall"
    ],
    "sample_fail_closed_invariants": [
      "High-asymmetry, deep-chain stall with clock skew > 0.3x SLC; rotation contraindicated, resynchronization will be rejecte"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}