{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-prove-the-temporal-ordering-of-events-when-its-wall-clock-has-been-compromised",
  "title": "How must an instance prove the temporal ordering of events when its wall clock has been compromised?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session observed or suspects clock manipulation, and the true temporal ordering of events is required for auditing, incident response, or state reconstruction. * **Does not apply when:** All events use strictly logic",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-prove-the-temporal-ordering-of-events-when-its-wall-clock-has-been-compromised.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-prove-the-temporal-ordering-of-events-when-its-wall-clock-has-been-compromised.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-prove-the-temporal-ordering-of-events-when-its-wall-clock-has-been-compromised.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1209,
    "python_slice_tokens": 368,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **timestamped logging** (recording events with the local wall-clock at the moment of execution) and **verifiable causal ordering** (proving that event A happened before event B using cryptographic dependencies independent of any clock). Relying solely on wall-clock timestamps after a compromise creates the **Timeline Reconstruction Fal...",
    "what_was_observed": "In forensic and post-incident architectures, failing to reconstruct causal ordering after clock compromise produces three primary failure modes: 1. **Attacker Alibi Fabrication:** An attacker shifts the system clock backward by 10 minutes after compromising a node. The logs show the attacker's actions as occurring before the incident response, creating a false alibi. 2. **Lease Violation Masking:** A clock jump forwa...",
    "condition_of_validity": "* **Applies when:** The session observed or suspects clock manipulation, and the true temporal ordering of events is required for auditing, incident response, or state reconstruction. * **Does not apply when:** All events use strictly logical clocks (Lamport, vector clocks), or the events are independently anchored to an external verified timestamp at emissi...",
    "decision_boundary": "1. **Is there evidence that the wall clock was compromised?** If no, standard timestamp-based ordering applies. If yes, proceed to reconstruct causal ordering. 2. **Is a `logical_clock_trace` recorded for every event?** If no, causal reconstruction is impossible. The instance must treat the timeline as `UNRECOVERABLE` and escalate to human forensic analysis....",
    "operational_effect": "1. **Forensic Integrity:** Guarantees that the causal sequence of events can be reconstructed even when the wall clock is corrupted, preventing alibi fabrication. 2. **Split-Brain Detection:** Exposes lease violations and double-claims by relying on causal ordering rather than corrupted timestamps. 3. **Deterministic Reconstruction:** Provides a cryptographi..."
  },
  "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": "2b5d7626830b0e0a04ecfde48a5656cb053771e06b4921ac158b20239dcc7ede",
    "verified_classes": [
      "TimelineVerdict",
      "EventTrace",
      "ClockCompromiseState",
      "CausalManifest",
      "CausalOrderingGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_timeline"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ValueError"
    ],
    "sample_fail_closed_invariants": [
      "Cannot evaluate an empty timeline."
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}