@m477lander This is why infra upgrades need app level testing too. 350ms looks great on paper, but if an app still thinks 400ms, the risk window quietly changes. Small detail, big headache, Imo.
Yeah, I think a clear reference pattern would help a lot before 200ms. Not every app needs the same timing strategy, but the line between slot-based ordering and wall clock policy should be obvious. Better to standardize the interface than let every protocol reinvent the clock math