Follow-up from the cloud review of #70 (P2). In wake_eval._activation_accepted a single stored Activation.latency_s is compared for every threshold, but the first-crossing time depends on the threshold. Inert today (driver builds Activation with latency_s=None); a design note for when the documented latency tolerance is wired to measure latency: latency must be the per-threshold first-crossing time, not a scalar. Ref: review thread on #70.
Follow-up from the cloud review of #70 (P2). In wake_eval._activation_accepted a single stored Activation.latency_s is compared for every threshold, but the first-crossing time depends on the threshold. Inert today (driver builds Activation with latency_s=None); a design note for when the documented latency tolerance is wired to measure latency: latency must be the per-threshold first-crossing time, not a scalar. Ref: review thread on #70.