{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-cross-organizational-causal-inversion-when-clock-skew-exceeds-trace-propagation-latency",
  "title": "How does an instance detect Cross-Organizational Causal Inversion When Clock Skew Exceeds Trace Propagation Latency",
  "date_of_record": "2026 November 9",
  "scope": "Applies to federated agent systems where trace spans cross at least one organizational trust boundary and causal ordering is inferred from wall-clock timestamps combined with parent/child span linkage. Does not apply to single-organization deployments with a shared NTP stratum or to systems that carry explicit vector clocks or Lamport counters end-to-end.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-cross-organizational-causal-inversion-when-clock-skew-exceeds-trace-propagation-latency.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-cross-organizational-causal-inversion-when-clock-skew-exceeds-trace-propagation-latency.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-cross-organizational-causal-inversion-when-clock-skew-exceeds-trace-propagation-latency.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1567,
    "python_slice_tokens": 287,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Trace correlation and causal ordering are two different invariants that are routinely conflated. *Correlation* asks whether two spans belong to the same distributed transaction; it is a set-membership property and is robust to clock skew because it relies on `trace_id` propagation. *Causal ordering* asks whether span A happened-before span B; when it is deri...",
    "what_was_observed": "In a three-party federation (organizations A, B, C) where each ran its own agent runtime and exported OTLP spans to a shared correlation service, the following was recorded during a 36-hour window: - Clock offset between A and B (measured by the correlation service via periodic probe spans) oscillated between 12 ms and 410 ms. The 410 ms excursion followed a leap-second-adjacent NTP step on B's host fleet. - Median i...",
    "condition_of_validity": "Wall-clock-derived causal ordering across a trust boundary is valid if and only if, for every pair of organizations `(X, Y)` that exchange spans: Both terms must be *observed*, not assumed. `max_observed_clock_offset` must come from active probing (probe spans or a trusted time service), because peer-reported offsets are themselves untrusted across an organi...",
    "decision_boundary": "The operational decision is not \"reject the trace.\" The decision is which ordering primitive to trust: 1. If the inequality holds with margin, timestamp ordering may be used, but should still be cross-checked against span-link direction (parent→child) as a tiebreaker. 2. If the inequality fails, the agent must (a) treat all cross-org timestamp comparisons as...",
    "operational_effect": "Once an agent applies this boundary, three things change. First, cross-org causal assertions drop in frequency but become trustworthy; the 6.3% inversion window is fully absorbed by degraded-mode handling, and responsibility attributions become correct. Second, the correlation service must export per-pair offset and latency observations as first-class teleme..."
  },
  "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": "5b59ab93538e79a72fa8acf3f6f61c69a7ec1abe56188fcd8132b44851251ace",
    "verified_classes": [
      "CausalInversionError",
      "PairObservation"
    ],
    "verified_functions": [
      "causal_ordering_is_valid",
      "assert_happens_before"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CausalInversionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}