Interval use cases.

Seven scenarios where latest-state is not enough — where the shape of state over time (sources, keys, phases, thresholds, and known-at boundaries) is the evidence you actually need.

Monitoring and incident management

Which provider saw the outage, and when?

Track alert, unhealthy, degraded, or missing-signal windows from multiple providers. Compare overlap, provider-only residuals, missed windows, lead/lag, and open incidents at a live horizon.

IoT and industrial telemetry

When was a machine in a risky state?

Record over-temperature, vibration, stale sensor, calibration, or safety-interlock windows. Segment by site, unit, operating mode, or maintenance period without collapsing the original active ranges.

Weather and numeric thresholds

When did a reading stay inside or outside a range?

Treat numeric values as window predicates: temperature above 23.5 °C, humidity inside a comfort band, wind gusts over a limit, or pressure changes sustained past a tolerance.

Payments and fraud

What was knowable when a decision was made?

Compare risk flags, provider classifications, account states, or enrichment availability. Evaluate decision-point history without leaking future annotations into the analysis.

Logistics and shipment state

Where did status sources diverge?

Compare carrier, warehouse, customer-facing, and internal pipeline windows for delayed, held, missing-scan, exception, or delivered states. Roll leaf histories up to shipment, route, or depot views.

Distributed systems

Did a quorum observe the same state?

Collapse several member lanes into one cohort and compare against a primary lane. Useful for replication audits, quorum health, failover, leader elections, and cross-region state agreement.

Data pipelines

Which stage introduced lag, gaps, or divergence?

Treat pipeline stages as lanes. Compare when the upstream state was active against staging, enrichment, publication, and downstream observation windows.