A gate_result decided last month renders identically to one decided yesterday. For a verdict to be trusted as a standing decision, it needs a freshness dimension:
- Surface
decided_at and the decision cohort size wherever a verdict is shown (view, gate output).
- Track how many new eligible traces/cases have arrived for the task since the decision cohort was sealed, and label the verdict fresh/stale accordingly ("decided 2026-07-30 · 412 new traces since").
- Optionally a cheap drift signal (e.g., input-length / tool-mix distribution shift between decision cohort and new traffic) as a stronger staleness cue than raw counts.
This is the trigger input for the continuous re-gate loop, but it is valuable standalone: even fully manual users should see when a verdict has gone stale.
A
gate_resultdecided last month renders identically to one decided yesterday. For a verdict to be trusted as a standing decision, it needs a freshness dimension:decided_atand the decision cohort size wherever a verdict is shown (view,gateoutput).This is the trigger input for the continuous re-gate loop, but it is valuable standalone: even fully manual users should see when a verdict has gone stale.