Get Current

What the cascade classifies RIGHT NOW, before the anti-churn dwell gate.

The published regime is the COMMITTED one, which by design lags the live inputs — so signals can stop meeting the committed regime's entry condition while that regime is still served. Without this block that reads as contradictory data: a consumer sees rationale saying "a security shock is active" next to a security_stress below the trigger, with no way to tell the difference between "stale by design" and "broken".

matches_committed false is normal and expected — it means a turn is being evaluated; read pending.count/needed for how far along it is.

A candidate regime accumulating confirmations but not yet committed.

Surfaced so a consumer can see a turn brewing before the committed regime actually changes (the anti-churn dwell gate requires needed consecutive samples before a switch).

How firmly the committed regime is holding — always present, always numeric.

pending is null exactly when the live cascade agrees with the committed regime, so a consumer polling for "is a turn brewing" gets a field that blinks in and out of existence and carries no signal on a hold. This block is the continuous companion: it is emitted on every response, candidate or not, so it can be differenced, thresholded, or fed to a risk sizer directly.

locked_for_s is the only HARD number here — the minimum-dwell floor mechanically prevents any change for that long. The one exception is a Structural Shock override, which is exempt from the floor by design.

Distance to every numeric boundary in the cascade — the raw material for client-side hysteresis.

The two CATEGORICAL inputs (quant_label, meme_season) have no distance by construction; read them from signals.