pub struct OutcomesOptions {
pub reason_window: Option<(u64, DateTime<Utc>)>,
pub rubber_stamp_threshold_ms: u64,
pub comparison_window: Option<(u64, DateTime<Utc>)>,
}Expand description
Fold-time options for the outcomes report (ticket
rubber-stamp-grant-flag). Pure-fold idiom preserved: the same log plus
the same options always yields byte-identical report data.
Fields§
§reason_window: Option<(u64, DateTime<Utc>)>Activity-cohort window for outcome reasons only; None means all recorded history.
rubber_stamp_threshold_ms: u64Grants APPROVED in under this many ms are flagged as rubber-stamp signals (strictly under; at/over is not flagged).
comparison_window: Option<(u64, DateTime<Utc>)>When Some((days, now)), the industry-comparison set (KRZ-333) is
folded over that window and attached to the report
(Outcomes::comparison). None keeps the fold hermetic — no git
probe, no clock — which is exactly the test seam: production
OutcomesOptions::resolve pins the documented default window and
the request time, so the purity rule above holds with the window as
an explicit input.