This partial result is not conclusive and does not pass the E2E benchmark.
For this measured configuration, RLM does not compensate as a generic CLI layer over Codex. The eight successful pairs show a preliminary quality signal (RLM 7/8 exact, direct Codex 6/8; mean delta +0.125), but the bootstrap interval is [-0.25, 0.5] and includes zero. The operational penalty is decisive: 149 calls versus 8, 13.2× more wall time, 2.7× more input tokens, and 56.6× more output tokens. One additional RLM attempt failed with an empty Codex response.
We stopped the planned 25-case RLM arm after this signal because continuing would consume substantial subscription runtime without a plausible cost/latency case for this CLI use. This is a scoped engineering recommendation, not a claim that RLM is unhelpful for every model or task.
- Planned cases:
25 - Paired successful cases:
8 - A: available
25, succeeded25, failed0, missing0 - B: available
9, succeeded8, failed1, missing16
- Verdict: not_demonstrated (not conclusive)
- Mean paired delta:
0.125 - Paired bootstrap 95%:
[-0.25, 0.5]
- A: calls
8, input tokens883337, output tokens4178, wall seconds121.98584629999823, failures0, subcalls0 - B: calls
149, input tokens2423172, output tokens236384, wall seconds1608.4929791999966, failures0, subcalls105
- A: calls
25, input tokens2766906, output tokens12223, wall seconds367.1852224999893, failures0, subcalls0 - B: calls
149, input tokens2423172, output tokens236384, wall seconds1637.1174710999985, failures1, subcalls105
- 17000253: {"message": "Codex returned an empty response", "type": "ValueError"}