Fill a Retry Docket Before the Second Pass
A second model pass should wait for a written docket. Cheap retries hide the real defect under fresh wording. Review time disappears when nobody names the stop rule. That rule belongs in the team wiki before the next generation. The page stays short enough to read during a handoff. The gate stays stricter than the prompt that failed. Public developer threads keep returning to retries and weak…
Before embarking on the second pass of a model, it is essential to have a written docket in place. This docket serves to prevent cheap retries, which merely mask underlying issues through rephrasing. The docket's importance lies in its ability to maintain a strict gate, ensuring that the model does not self-judge its repairs. The docket's purpose is to make the cost of retries transparent, akin to a ferry needing a paper slip to depart.
Three roles are assigned to maintain this process: the Patch Author, the Docket Clerk, and the Host Steward. Each role has specific responsibilities to prevent a loop from turning into a silent rewrite. The docket, resembling a library hold slip, records the failing check and the condition that ends the loop. This structure ensures that retries are treated with caution, as a missing field in the docket sends the work back to the author for correction.
The steward's role involves running the same failing command on the practice host before and after the second pass, with the clerk ultimately closing the docket with one of three outcomes: fixed, still failing, or requiring a human rewrite.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
