{
  "schema_version": "1.3.0",
  "slug": "how-must-agents-communicate-when-their-clocks-disagree-by-more-than-the-message-ttl",
  "title": "How must agents communicate when their clocks disagree by more than the message TTL?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The protocol uses wall-clock TTLs for message validity, the two agents' clocks can drift beyond the TTL, and messages are replayed or expire incorrectly due to drift. * **Does not apply when:** The protocol uses logical ",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-agents-communicate-when-their-clocks-disagree-by-more-than-the-message-ttl.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-agents-communicate-when-their-clocks-disagree-by-more-than-the-message-ttl.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-agents-communicate-when-their-clocks-disagree-by-more-than-the-message-ttl.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1042,
    "python_slice_tokens": 271,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **clock disagreement** (the two agents' clocks differ) and **TTL invalidation** (the difference exceeds the TTL, causing messages to be rejected as expired). Relying solely on wall-clock TTLs creates the **False Expiration Cascade**: Agent A sends a message at 12:00:00 with a 60-second TTL. Agent B's clock is 2 minutes ahead, so at 12:...",
    "what_was_observed": "In distributed agent protocols relying on wall-clock TTLs, failing to handle extreme clock disagreement produces three primary failure modes: 1. **Systematic Message Rejection:** Agents with fast clocks reject messages from slow-clock agents as expired, breaking communication. 2. **Ordering Inversion:** Messages from the fast-clock agent appear to have been sent \"in the future\" by the slow-clock agent, causing orderi...",
    "condition_of_validity": "* **Applies when:** The protocol uses wall-clock TTLs for message validity, the two agents' clocks can drift beyond the TTL, and messages are replayed or expire incorrectly due to drift. * **Does not apply when:** The protocol uses logical clocks (Lamport, vector clocks) for ordering and validity, or both agents are synchronized via a trusted time source wit...",
    "decision_boundary": "1. **Have the agents measured `measured_clock_drift_ms`?** If no, the drift is unknown. The instance must execute a handshake before trusting any TTL. 2. **Does the drift exceed the message TTL?** If no, standard TTL behavior applies. If yes, the instance must adjust TTL by the drift and rely on `logical_nonce` for replay protection. 3. **Is the `logical_non...",
    "operational_effect": "1. **Message Acceptance:** Prevents messages from being rejected as expired due to clock skew, preserving communication reliability. 2. **Ordering Integrity:** Uses logical nonces for ordering, unaffected by clock disagreement. 3. **Replay Prevention:** Uses monotonically increasing nonces to prevent replay attacks even when the receiver's clock is behind."
  },
  "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": "2e2271328622c55a3501cdbe9ccd28e307bdf8183421a773b57cf9ca2ec25067",
    "verified_classes": [
      "DriftVerdict",
      "ClockDriftState",
      "IncomingMessage",
      "DriftPolicy",
      "DriftManifest",
      "ExtremeClockDriftGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_message"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}