Compare two histories by aligning their windows.

Problem

Interval joins become brittle quickly.

Two providers can overlap partially, miss each other entirely, disagree only inside a segment, or leave a gap between active ranges. Hand-written interval joins tend to hide these cases in query logic.

Solution

Declare the comparison plan before emitting rows.

A comparison plan names the target lane, the against lane, the scope, the normalization policy, and the row families to emit. That order is important because it keeps the interpretation visible instead of burying it inside interval-join code.

var result = pipeline.History
    .Compare("Provider QA")
    .Target("provider-a", s => s.Source("provider-a"))
    .Against("provider-b", s => s.Source("provider-b"))
    .Within(scope => scope.Window("DeviceOffline"))
    .Normalize(n => n.RequireClosedWindows().HalfOpen())
    .Using(c => c.Overlap().Residual().Missing())
    .Run();

How

Declare the plan in the same order you reason about it.

Start with the business question: which lane is being tested, which lane should explain or cover it, and which window family is in scope. Then decide how time should be normalized before the comparator row families are selected.