Happened-before¶
The least strict partial order on distributed events generated by local program order, message send-before-receive, and transitivity, capturing potential causality without assuming synchronized physical clocks.
Core Idea¶
Lamport's happened-before relation a→b holds when a precedes b in one process, a sends a message received at b, or a→c→b; unrelated events are concurrent. Local order and communication propagate causal influence; logical clocks assign increasing timestamps consistent with the relation, though scalar timestamps cannot characterize concurrency conversely. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.
Scope of Application¶
Happened-before belongs to distributed systems and is useful where the analyst can specify events in processes, within-process order, message send and receive pairs and transitive closure, then evaluate the relation contains exactly the generating program and message edges plus transitive consequences and remains irreflexive and acyclic. The scope is broad within that domain but bounded by the need for the relation contains exactly the generating program and message edges plus transitive consequences and remains irreflexive and acyclic. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.
Clarity¶
The abstraction clarifies a crowded vocabulary by making the relation contains exactly the generating program and message edges plus transitive consequences and remains irreflexive and acyclic the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Happened-before can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.
Manages Complexity¶
Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Happened-before. Happened-before compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.
Abstract Reasoning¶
- Identify the carrier. State what the elements, states, objects, or observations are: events in processes, within-process order, message send and receive pairs and transitive closure. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the relation contains exactly the generating program and message edges plus transitive consequences and remains irreflexive and acyclic independently of one notation or implementation.
Knowledge Transfer¶
Knowledge transfers strongly among subfields of distributed systems because they reuse events in processes, within-process order, message send and receive pairs and transitive closure, Local order and communication propagate causal influence; logical clocks assign increasing timestamps consistent with the relation, though scalar timestamps cannot characterize concurrency conversely., and type the carrier, state every parameter and convention in the definition, test that the relation contains exactly the generating program and message edges plus transitive consequences and remains irreflexive and acyclic, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction Happened-before Domain-specific
Parents (1) — more general patterns this builds on
-
Happened-before is a kind of Causality Prime
The proposed strict upward parent is
prime:causality.
Hierarchy path (1) — routes to 1 parentless root
- Happened-before → Causality → Dependency
Neighborhood in Abstraction Space¶
Happened-before sits in a crowded region of the domain-specific corpus (35th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Concurrency, Transactions & Process Coordination (20 abstractions)
Nearest neighbors
- Communicating sequential processes — 0.91
- Shared memory — 0.90
- Live distributed object — 0.90
- Inter-process communication — 0.90
- Event structure — 0.90
Computed from structural-signature embeddings · 2026-09-08