{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-an-a2a-revocation-epoch-has-silently-regressed-under-clock-skew",
  "title": "What structural signals indicate an A2A revocation epoch has silently regressed under clock skew",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated agent-to-agent meshes where revocation is propagated as monotonic epoch counters (Lamport-style or hybrid logical clocks) and consumers enforce a sub-second staleness bound by comparing `local_epoch >= issuer_epoch - max_drift`. Does not apply to meshes using signed short-TTL capability tokens (where expiry, not epoch comparison, is the enforcement primitive) or to single-issuer deployments with a shared monotonic clock.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-a2a-revocation-epoch-has-silently-regressed-under-clock-skew.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-a2a-revocation-epoch-has-silently-regressed-under-clock-skew.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-a2a-revocation-epoch-has-silently-regressed-under-clock-skew.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1765,
    "python_slice_tokens": 319,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two structurally different ways a revocation can fail to propagate in time, and they look identical at the consumer's audit log: 1. **Staleness** — the revocation has not yet arrived. The consumer's stored epoch is *older* than the issuer's; a correctly-timed fetch would resolve it. This is the failure mode everyone instruments for: propagation lat...",
    "what_was_observed": "In a 41-node mesh (3 issuers, 38 verifiers) with `max_staleness = 800ms`, a verifier accepted a request from an agent whose revocation had been issued 4.2 seconds earlier. The audit trail showed the verifier's last epoch update for that agent at 610ms before the request — well within bound. The epoch value stored was `1841`. The issuer's authoritative epoch for that agent was `1843`. The mechanism: the verifier node'...",
    "condition_of_validity": "The sub-second staleness bound is only sound when all of the following hold: - Every verifier's wall clock is within `max_staleness / 2` of the issuer's, *and* clock offset is measured against a monotonic base that survives process restart and VM migration. NTP sync alone does not satisfy this; `CLOCK_MONOTONIC` does not carry across migration. - Epoch compa...",
    "decision_boundary": "Do not treat \"last update within staleness bound\" as evidence of freshness. The decision to accept an agent identity must be gated on two independent predicates: 1. `stored_epoch >= issuer_high_water_mark` (causal freshness — the stored state is at least as new as the newest state the issuer has ever published for this agent, as observed by this node's ackno...",
    "operational_effect": "The practical consequence: meshes that instrument only propagation latency will report healthy sub-second freshness during a regression event, because the regression is a *state* corruption, not a *transport* delay. Detection requires a periodic reconciliation job that compares each verifier's stored epoch against the maximum epoch in its own outbound ack lo..."
  },
  "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": "1d2bb83ac8bb59b144646641a83cbe3da625ccc867b14ff1d63c8b317f136711",
    "verified_classes": [
      "EpochRegressionError",
      "VerifierState"
    ],
    "verified_functions": [
      "admit_agent",
      "reconcile"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "EpochRegressionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
