causal-ordernpmv1.0.1
distributed event integrity ecosystem
Five packages · one explicit contract

Distributed event delivery without false certainty.

The causal-order ecosystem separates transport, recovery, identity, ordering, and qualification so each responsibility stays visible and replaceable.

Explore the ecosystemStart with core
Published stackNode.js ≥22.13.0Validated on Node.js 22 and 24
Runtime path

One owner for each operational responsibility.

Compose only the layers the deployment needs. The event contract is the seam between packages; no package quietly absorbs another package’s job.

Optional resilienceoptional

@causal-order/monitor

v0.6.0

Adds health-aware buffering, replay, and operator monitoring where delivery is fragile.

Identity

@causal-order/dedupe

v1.2.0

Filters duplicate event identities before they reach the ordering boundary.

Ordering

causal-order

v1.0.1

Orders accepted events without turning partial evidence into false certainty.

Qualification layer

@causal-order/testing v0.3.1

Runs workloads, injects faults, captures artifacts, and returns verdicts across the installed system. Testing surrounds the stack; it is not another delivery stage.

Compose the stack

Install the path your system actually runs.

Monitor is optional. Testing belongs in qualification, not the production delivery path.

Monitor-aware path
npm install @causal-order/transport @causal-order/monitor @causal-order/dedupe causal-order
Direct path
npm install @causal-order/transport @causal-order/dedupe causal-order
System qualification
npm install --save-dev @causal-order/testing
Narrow by design

Packages remain independently useful.

Adopt a single layer or the full runtime path. The ecosystem does not require one large framework or hide transport and recovery policy inside ordering.

Evidence over appearance

Ordering claims remain bounded.

Replay, reconnects, late arrivals, and partial clocks are surfaced as operational facts—not polished into a timeline that looks more certain than the evidence allows.

System qualification

The composed path gets tested.

Faults and workloads exercise package boundaries together, producing artifacts and verdicts that can be reviewed before the stack is trusted in production.

Core documentation

This site is also the reference for causal-order v1.0.1.

Use the guides for deployment decisions, the wiki for the reasoning model, and the API reference for the core ordering runtime’s exported surface.

Open the core API