plan-cache-rollout-gate

To evaluate plan-cache metrics before a rollout, you aggregate data across the larger window of the last 30 pipeline sessions or 14 days. This applies three thresholds to emit a JSON verdict with evidence for your flip-to-on PR.

A data-driven rollout gate aggregates plan-cache metrics across pipeline sessions to decide if a feature can flip from shadow to on. It removes guesswork by applying threshold checks and providing a structured JSON verdict for evidence-based deployments.

You aggregate pipeline session data by reading plan-cache audit outputs and evaluating them over the larger of the last 30 sessions or 14 days. This produces a ROLLOUT_GATE_PASS, FAIL, or INSUFFICIENT_DATA verdict for your PR.

You need to check rollout gate thresholds before authoring the flip-to-on PR. Checking thresholds over the larger of 30 pipeline sessions or 14 days ensures you have sufficient data to prevent unsafe, unobservable rollout decisions.

An INSUFFICIENT_DATA verdict means your plan-cache metrics did not meet the minimum window requirement of 30 pipeline sessions or 14 days. You must wait for more pipeline data before attempting to flip the rollout gate from shadow to on.

You can use the rollout gate metrics, but applying the gate requires the larger window of the last 30 pipeline sessions or 14 days. If you lack this volume, the aggregation will emit an INSUFFICIENT_DATA JSON verdict instead of a pass or fail.