Close shifted oracle frontier boundaries

docs/opprof/oracle-gap-protocol.md

@@ -1,11 +1,32 @@
 # Static-policy oracle-gap protocol
 
-Status: **FROZEN WITH A-OG-1, A-OG-2, AND A-OG-3 AMENDMENTS**.
+Status: **FROZEN WITH A-OG-1 THROUGH A-OG-4 AMENDMENTS**.
 
 Date frozen: 2026-07-13 (Asia/Singapore). Existing Phase-3 measurements were
 inspected only to choose the workload pair and rate brackets. They are
 exploratory calibration data, not primary observations in this protocol.
 
+### A-OG-4 — close a majority-shifted boundary (before confirmation scores)
+
+After all four primary frontiers and 70 scores were complete, the controller
+was interrupted before the first confirmation produced a score. The partial
+`P01-C10-r26-rep1` attempt contained no result, sanity file, or score and is
+archived separately. This amendment is therefore blind to confirmation
+outcomes.
+
+The original confirmation schedule still runs first. Afterward, each cell's
+majority-vote frontier is recomputed. If either side of the *actual* final
+boundary has fewer than three trials because the provisional boundary moved,
+the controller runs only enough repetitions at that existing rate to reach
+three, high-to-low, on a fresh server for that config. It then recomputes the
+boundary and repeats for at most three closure rounds. No new rate anchor may
+be added. Failure to obtain a monotone, bracketed boundary with three trials
+per side within three rounds or the 6 H20-hour cap makes the experiment
+inconclusive.
+
+This fills a stopping-rule omission: it does not change any existing score,
+majority rule, phase, config, rate grid, SLO, or oracle calculation.
+
 ### A-OG-3 — freeze a per-logical-trial transport retry rule (after 62 scores)
 
 The first attempt at `P06-C10-r1.9-rep0` reproduced the same isolated local