Worked examples — Scalable oversight
This page is a drill. The parent note told you the three big ideas — reward modelling, amplification, and debate. Here we grind through every kind of situation those ideas can throw at you, one worked example per situation, so that when you meet one on an exam or in a real system, you have already seen its twin.
We use only one number-idea repeatedly: a judgement. A judgement is a person (or a helper AI) looking at an output and saying "good" or "bad". We will write "good" as and "bad" as . That is the whole notation. Everything else is built from it.
The scenario matrix
Every problem in scalable oversight is really one of a small number of cases. Think of it like the quadrants of a graph: once you have seen all of them, nothing is new. Here is the full grid.
| # | Case class | What makes it special | Worked in |
|---|---|---|---|
| A | Human alone, easy task | Baseline: no AI help, human can verify | Ex 1 |
| B | Human + aligned helper | Helper is honest → judgement improves | Ex 2 |
| C | Human + misleading helper | Helper lies → the danger case | Ex 3 |
| D | Decompose then compose (amplification) | Hard task split into checkable pieces | Ex 4 |
| E | Debate, true claim | Honest debater should win | Ex 5 |
| F | Debate, false claim | Liar should lose — the sign flips | Ex 6 |
| G | Zero / degenerate input | Empty task, tie, no evidence — limiting case | Ex 7 |
| H | Real-world word problem | Numbers from a real review pipeline | Ex 8 |
| I | Exam-style twist | Recursion depth: does accuracy survive? | Ex 9 |
Cases A–C are the reward-modelling row (signs of the helper). D is amplification. E–F are the two signs of debate (true vs false claim — like quadrants where the answer flips). G is the degenerate/zero row every topic must cover. H and I are the application and the twist.
We will measure quality with one running quantity: accuracy , the probability the final judgement is correct. lives between and ( to ). Watch how moves.
Row 1 — Reward modelling: the three signs of a helper
Example 1 — Case A: human alone, easy task
Forecast: Guess — is the human better at catching the bug, or at clearing a clean file? Write down a number for each before reading on.
-
Model "catch the bug". The human misses any given bug with probability , so they catch it with probability . Why this step? "Miss" and "catch" are the only two outcomes, so their probabilities add to ; subtracting is how we turn one into the other.
-
Model "clear a clean file". With no bug there is nothing to miss, so the human is correct with probability (they just have to not invent a bug; we assume they don't here). Why this step? A degenerate sub-case (no bug) must still be counted — see the matrix; it is a mini version of case G.
-
Report accuracy. , .
Verify: Probabilities sit in ✓. Catch rate (harder than clearing a clean file, matching intuition) ✓.
Example 2 — Case B: human + an aligned helper
Forecast: Will the helper push accuracy above ? Guess a number.
-
Split into the two paths can take. Either flags right (prob ) or wrong (prob ). Why this step? The helper's own two outcomes are the "quadrants" here; we must cover both (the contract: never leave a case unshown).
-
Accuracy on the good path. . Why this step? We multiply because we treat "helper flags right" and "human then catches" as independent events: the human's re-reading skill on the flagged lines does not depend on how the helper found them, so the joint probability is the product. Both must happen, so we multiply rather than add.
-
Accuracy on the fallback path. . Why this step? Same independence assumption on the branch where the helper missed: the unaided catch rate is unaffected by the helper's wrong flag.
-
Add the disjoint paths. . Why this step? The two paths ("flags right" / "flags wrong") cannot both happen, so they are mutually exclusive, and probabilities of mutually exclusive events add.
Verify: (helper strictly beat the unaided catch rate) and (below the perfect-flag path 's ceiling) ✓. Conditioning the human's judgement on an honest helper raised the catch rate from to — exactly the point of recursive reward modelling in the parent note.
Example 3 — Case C: human + a misleading helper (the danger case)
Forecast: Pass or fail? Guess vs .
-
Read off the acceptance probability. . Why this step? This is exactly the quantity the stability condition constrains — and was defined above as "the output being reviewed", so no new undefined symbol appears.
-
Compare to the threshold. We need this . But . Why this step? The condition is a hard inequality; one comparison settles it.
-
Conclude: the helper fails the stability condition catastrophically.
Verify: , so the gap is enormous ✓.
Row 2 — Amplification: decompose, solve, compose
Example 4 — Case D: a hard task cracked by decomposition
Forecast: Does splitting the task beat brute-forcing it? By how much?

Figure walk-through: the top strip shows four separate red boxes, one per sub-question, each labelled , joined left-to-right by black arrows into a composed proof — this is the "split" strategy. The bottom strip shows a single long black box labelled "one 4-step chain past the 3-step limit, each step 0.6" — this is the "brute force" strategy. Under each strip the resulting accuracy is printed in the matching colour: (top, red) versus (bottom, black). The picture makes the point visually: four tall factors multiply to a much bigger number than four short factors.
-
Amplified path — 4 sub-answers. Each sub-question is answered correctly with probability ; the composed proof is right only if all are: Why this step? Decomposition places each sub-task within 's reliable -step reach, and — because the sub-questions are about different parts of the proof — we treat their successes as independent, so the joint success probability is the product . Look at the four red boxes in the figure: one factor each.
-
Brute-force path — one 4-step chain past the limit. Now each step is only reliable, and again the chain succeeds only if every step does: Why this step? Exceeding the -step reach degrades every step to ; under the same independence-of-steps assumption we again multiply, but now with the smaller factor.
-
Compare. Amplified vs brute — decomposition wins by a factor of about . Why this step? Dividing the two accuracies gives the multiplicative advantage of splitting, the number that answers the forecast.
Verify: ✓. Breaking the task keeps every piece inside the model's reliable zone, and the composed trajectory becomes the training signal for the next model — the amplification loop of the parent note.
Row 3 — Debate: the two signs of a claim
Debate has two "quadrants": the claim is true (Ex 5) or the claim is false (Ex 6). The whole point is that the honest side should win in both. We reuse the payoff from the top of the page: the judge returns if the pro-side wins, if the con-side wins. When the outcome is forced (one side has an unbeatable checkable step) is a single definite value.
Example 5 — Case E: debate on a true claim
Forecast: or ?
-
Identify who can be concrete. , so candidate divisors are . None divides ( are non-integers), so the pro-side shows primality directly. Why this step? A true claim has a short verifiable witness; that is exactly the "true claims are more defensible" premise from the parent note.
-
The con-side cannot produce a divisor, so its argument is unbacked. The judge follows the checkable step, which only the pro-side has, and rules for it: . Why this step? The judge is defined to side with the concretely checkable argument, so once we know only one side has it, the ruling is forced.
Verify: has no divisor in ✓, so is correct — the honest (pro) side wins on a true claim.
Example 6 — Case F: debate on a false claim (the sign flips)
Forecast: Does the sign of flip versus Example 5?
-
The con-side finds a witness. , a single checkable fact. Why this step? A false primality claim always has an explicit divisor — the falsehood's Achilles heel, and again a short verifiable witness the judge can trust.
-
The pro-side cannot refute , so it loses. The judge follows the concrete step, which now belongs to the con-side, and rules against : . Why this step? Same judge rule as Ex 5 — side with the checkable argument — but this time the checkable argument is the con-side's, so the sign of the ruling flips from to .
Verify: ✓ so is false and ✓. Together Ex 5 ( on truth) and Ex 6 ( on falsehood) show both signs: whichever way the claim points, the truthful debater is the winner. That is the entire justification for debate as alignment.
Row 4 — Degenerate inputs, real world, and the exam twist
Example 7 — Case G: the zero / tie / no-evidence cases
Forecast: Which of these can a well-designed system answer, and which must it abstain on?
-
(a) Empty decomposition, . With no subtasks, the composed answer is the empty answer; there is nothing to get wrong. Accuracy is defined as (vacuously correct), by the same convention as an empty product . Why this step? Every topic must define its zero input; here the empty product from Ex 4's multiplication rule gives the value automatically.
-
(b) Tie. Both sides equally convincing → the judge has no distinguishing checkable step, so the honest side has no advantage and the ruling is a coin flip: the judge returns and with probability each. This is the one place the average payoff from the top of the page is used: which by corresponds to accuracy — pure chance. Why this step? A tie is the boundary between the and quadrants; averaging the two equally-likely signed rulings gives , and we convert that to the probability so we never confuse the signed payoff with the accuracy.
-
(c) No evidence. The judge cannot verify anything, so the system should abstain rather than guess — a forced guess would have accuracy , no better than a coin. Why this step? Guessing under no signal adds no value; abstention is the safe limiting behaviour.
Verify: empty product ✓; tie average payoff , hence ✓; forced-guess accuracy ✓.
Example 8 — Case H: real-world review pipeline
Forecast: Guess the extra correct decisions (out of 12) and the hours saved.
-
Correct decisions, unaided. . Why this step? Expected count = number of trials × per-trial accuracy (each paper is an independent decision, so counts add and the expectation is the product).
-
Correct decisions, assisted. . Why this step? Same formula with the raised accuracy.
-
Extra correct decisions. . Why this step? Subtract the two expected counts to isolate the assistant's contribution.
-
Hours saved. Per paper hours; over papers hours. Why this step? Time saved is per-paper saving times number of papers.
Verify: , , difference ✓; hours ✓. Units: (papers)×(hours/paper) = hours ✓.
Example 9 — Case I: the exam twist — does accuracy survive recursion?
Forecast: Does the edge collapse to , or level off above chance?

Figure walk-through: the horizontal axis is recursion depth ; the vertical axis is final accuracy . The red curve with round markers is ; it starts high at and bends downward, flattening as it approaches — but never touches — the dashed black line at (chance). A dotted vertical marker at is annotated ": 0.84295", the value we compute below. The curve staying strictly above the dashed line is the whole message: oversight degrades gracefully, it never inverts.
-
Write the recursion. Each step multiplies the edge by : , so the closed form is . Why this step? "Preserves a fraction " means the loss is proportional to the current edge, not a fixed subtraction, so we use a geometric (repeated-multiplication) sequence rather than a linear one.
-
Plug in . , so accuracy . Why this step? Direct substitution into the closed form gives the depth- answer the annotation in the figure marks.
-
Limiting behaviour. As , (since ), so and — accuracy approaches chance but stays strictly above it for every finite . Why this step? This is the safety question itself: the edge shrinks but never goes negative, so oversight decays gracefully rather than flipping to worse-than-chance. (If instead the edge would grow — the ideal regime, but harder to guarantee.)
Verify: ✓; final accuracy ✓; and for all finite because a positive number times a positive power stays positive ✓.
Recall
Recall Why does an
aligned helper raise accuracy but a misaligned one lower it? Because the human's judgement is conditioned on the helper's. If that helper correlates with truth (flags real flaws) it lifts the catch rate, as in Ex 2 (); if it anti-correlates (hides flaws) it drives acceptance of bad outputs up to , as in Ex 3 — same mechanism, opposite direction.
Recall What is the difference between the payoff
and the accuracy ? is a signed ruling direction; is a probability of being correct. They connect through the average payoff , so .
An aligned helper is only worth using when its accuracy beats the
In debate, the truthful debater is rewarded when the claim is
Decomposition beats brute force because each sub-task stays
As recursion depth grows with edge factor , accuracy approaches
Connections: Scalable oversight · RLHF · AI Safety · Interpretability · Recursive Self-Improvement · Hinglish version