Affects
Teams that use the Tracer rules engine and have treated the previous per-expression latency statement as a performance commitment.
What changed
The documentation no longer states that every compiled CEL expression evaluates in under one millisecond. It now describes the implemented execution model: Tracer evaluates compiled expressions during validation. This is a documentation correction. It does not announce a runtime change or establish a latency guarantee.
Impact
Classification: Review recommended. Do not use the former sub-millisecond statement as an SLA, capacity assumption, or performance commitment.
What you need to do
Review any sizing, latency, or customer-facing commitments that relied on the removed statement. Measure rule evaluation in your own deployment for the rule sets and load you operate.