Close a Flake Freeze Only When the Replay Budget Hits Zero
An agent patch earns a flake freeze only when three records agree: a named property contract, one fixture identity across the replay set, and a replay budget that has already hit zero on a single failure signature. A quiet log from a free server does not satisfy that rule. A draft produced through free model access does not satisfy it either. That split is the strategy. Execution cost and test…
An agent patch gains a flake freeze status only when three conditions are met: a named property contract, a consistent fixture identity across the replay set, and a replay budget that has been depleted on a single failure signature. This rule is strictly enforced, and free server logs or test runs on free model access do not meet these criteria.
The process separates execution cost and test authority, ensuring a clear distinction between them. Mixing these aspects can lead to a blinking assertion being mistakenly labeled as noise or a real invariant break being ignored. This article outlines a local decision procedure to address this split, without providing a benchmark, quota, hardware details, or model name.
The Python gate, which is presented later in the piece, is merely an unexecuted reference implementation that does not make any network calls.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
