HackerPapers

arXiv:2605.09114cs.DC

Light Cone Consistency: Closure, Ordering, and the Single-Observer Boundary

Rob Landers, Kaben Kramer

Early discovery. Linked by one identifiable commenter. This paper is outside the main ranking; a mention is not an endorsement.

Abstract

Every distributed system is a message-passing system, and every message-passing system is a growing causal DAG observed by a set of observers. We treat each observer's consistency as two operators on its visible sub-DAG (a causal-closure filter $C$, fixing which dependencies it must have seen, and a fork resolution $O$, ordering the concurrent forks the filter admits) and give the resulting space the structure the flat catalog of named models lacks. The operators are coupled, asymmetrically: an order that refines causality supplies closure its filter never demanded. That coupling yields a decidable readability order (which configuration's data another can read honestly) with a factoring dichotomy: the order splits across the $C$ and $O$ axes exactly when ordering does not refine causality, and refuses to when it does, the cross-axis gap being the closure ordering supplies. On that order sit a consistency ratchet (a level lost under migration is never regained) and a Detection = Prevention bound: a system can tell its order inverted causality only if it retained exactly what would have prevented the inversion. The classical results land at clean coordinates in the same system, not as new claims: resolving a fork demands retaining the causal history that distinguishes its branches (database folklore, here an impossibility for every message-passing system) and linearizability resolves as a composite of two systems, a store and a global real-time serializer supplying an order no single observer's light cone can. The named models are configurations of $(C, O)$, exact over the standard-safety fragment and generative past it, predicting configurations the catalog has not named. LCC is a formalization of the observer-relative consistency model of Burgess and Gerlits.

arXiv comments
32 pages, 4 figures, 3 tables. Preprint of work submitted to DISC 2026
Journal reference
DOI
Subjects
cs.DCDistributed, Parallel, and Cluster Computing

On Hacker News

Linked by 1 identifiable commenter in 1 comment across 1 thread, from Jul 2026 to Jul 2026. Found in 2 HN submissions from May 2026 to May 2026. Open submission discussions.

Comments linking this paper, per year.

Discussed in comments1 thread

    • They are indeed quite challenging. We literally wrote a paper about it (https://arxiv.org/abs/2605.09114) ... you almost describe some of our original architecture too! You might find it interesting -- or not. https://getswytch.com

      withinboredomView on HNParent context

Submitted to Hacker News

  • LCC: Toward a Unified Theory of Consistency in Message-Passing Systems
  • Show HN: Self-hosted Spanner-like database that speaks Redis

    Almost 10 years ago, I was working on two projects: a space game that simulated relativity and a "dead man's switch" in case I died. I realized two things back then: 1. If I wanted to leave a message for my son in 30 years, I couldn't make any assumptions about technology in the future. 2. No database is unkillable. Over the coming decade, I set out to figure out how to build a leaderless database that could go "holographic" -- any partition could create a completely independent cluster…

Connected through shared HN threads, not inferred similarity or a recommendation.