{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-s-replay-clock-diverges-from-its-persisted-causal-watermark-in-multi-agent-incident-reconstruction",
  "title": "What happens when an instance's replay clock diverges from its persisted causal watermark in multi-agent incident reconstruction",
  "date_of_record": "2026 November 16",
  "scope": "Applies to deterministic replay of multi-agent incident timelines where each agent emits events stamped against a logical clock and a persisted causal watermark (vector clock or Lamport frontier) is used to order cross-agent events during reconstruction. Does not apply to single-agent replay, nor to systems where the replay clock is reconstructed entirely from a total-order commit log (e.g., a single-writer append-only bus).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-s-replay-clock-diverges-from-its-persisted-causal-watermark-in-multi-agent-incident-reconstruction.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-s-replay-clock-diverges-from-its-persisted-causal-watermark-in-multi-agent-incident-reconstruction.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-s-replay-clock-diverges-from-its-persisted-causal-watermark-in-multi-agent-incident-reconstruction.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1453,
    "python_slice_tokens": 225,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two clocks in any forensic replay of a multi-agent incident: the **emission clock** (what the agent believed the time was when it wrote the event) and the **causal watermark** (the highest logical frontier the agent had durably observed and persisted before writing). These are not the same value, and they are not guaranteed to be consistent at repl...",
    "what_was_observed": "In a four-agent pipeline (planner, retriever, executor, verifier) replaying a 90-second incident, the harness reconstructed 1,412 events. The re-execution ran ~40× faster than wall time. Because the harness advanced its virtual clock only on explicit `sleep` calls and not on CPU-bound decision loops, three executor events that originally occurred *after* a verifier rejection were reconstructed as occurring *before* i...",
    "condition_of_validity": "A replayed event `e` with reconstructed emission clock `c_e` and persisted causal watermark `W_e` is admissible into the forensic timeline only if: and, for the *next* event `e'` in the same agent's stream, `W_e ≤ c_{e'}` (monotone watermark advance). When both hold for all events, the reconstructed ordering is causally consistent with what each agent could ...",
    "decision_boundary": "- **If all events satisfy `c_e ≤ W_e` and watermarks are monotone:** emit a total order; the reconstruction is forensically admissible. - **If any event violates `c_e ≤ W_e`:** do not silently clamp the clock. Clamping hides the drift and produces a total order that is wrong in exactly the cases that matter. Instead, mark every event in the violating agent's...",
    "operational_effect": "Teams that skip the domination check ship incident reports with inverted causality roughly whenever replay speed diverges from incident-time speed — which is nearly always. The failure is silent because re-simulation is *deterministic*: it reproduces the same wrong order every time, so it looks reproducible and therefore trustworthy. The persisted watermark ..."
  },
  "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": "59a674b5b6fbf65ba94a87960063bcd9335ce6710531ee242efd5a9601038f1f",
    "verified_classes": [
      "CausalDriftError"
    ],
    "verified_functions": [
      "validate_replay_event",
      "order_timeline"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CausalDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
