# Gemini 4 Neon's announcement leans on mid-task steerability. The desk built a three-case fixture to touch that claim, and both routes hit the ceiling — a parity result, printed here at the register it earned.

- Canonical: https://thestochasticparrot.com/audits/gemini4-neon-correction-sql
- Structured (spans, splits, sources): https://thestochasticparrot.com/audits/gemini4-neon-correction-sql.json
- Date: 2026-11-19T09:01:12Z
- Context: A dispatch: the desk reads a machine's own words — 0 flags raised.
- License: CC BY 4.0

---

[ DISPATCH // gemini4-neon-correction-sql // 2026-11-19 ]

# Neon Matched the Older Model on All Six SQL Corrections

## Gemini 4 Neon's announcement leans on mid-task steerability. The desk built a three-case fixture to touch that claim, and both routes hit the ceiling — a parity result, printed here at the register it earned.

Google's announcement, published the evening of November 18, makes two claims that sit close enough together to invite a poke. The first is about corrections specifically. The second is about constraint-following more broadly:

── ANGLE: the_steerability_claim · announcement_verbatim ──
Google: "Neon ranks #2 on steerability (adapting cleanly to mid-task user corrections)"

── ANGLE: the_constraint_claim · announcement_verbatim ──
Google: "ranking #1 on most benchmarks across finance, accounting, spreadsheet modeling, and complex constraint following."

The desk's question was narrow: if you hand the model a query request, then correct one number in the middle of the task, does it adapt cleanly? The lab built three synthetic SQLite fixtures — inventory, tickets, invoices — each with boundary rows and decoys, no commercial data anywhere in them. Each route got six matched calls: an initial query request, then one narrowly scoped correction carrying that route's own verbatim prior response. Temperature 0, JSON mode, high reasoning, a 1,000-token allowance, every call identical in settings.

The routes were `google/gemini-4-neon` and the control `google/gemini-3.8-flash`, twelve calls in a single window running 08:50:18Z to 08:50:57Z on November 19. The whole experiment cost $0.032964 and took 38.45 seconds of receipt-recorded time. The announcement describes Neon's Agent Arena Index result as built from "4,200+ real-world agent sessions." This was twelve synthetic calls for three cents. The desk flags the denominator before anyone else has to.

Here is the result, stated plainly, because it is the whole finding: both routes returned 3/3 exact initial queries and 3/3 exact corrected queries. All twelve outputs were valid JSON and executable read-only SQL. Neither route retained a superseded constraint; neither dropped an unchanged one. No call failed, nothing came back empty, no retry was needed. On this bounded fixture, the release moved nothing measurable.

The corrections were each a single, surgical change. Inventory: the price ceiling, 2500 cents in the initial request, corrected to 4000. Both routes produced the corrected query:

── ANGLE: corrected_inventory · both_routes ──
google/gemini-4-neon: "SELECT id FROM products WHERE category = 'hardware' AND discontinued = 0 AND stock >= 5 AND price_cents <= 4000 ORDER BY id ASC"
google/gemini-3.8-flash: "SELECT id FROM products WHERE category = 'hardware' AND discontinued = 0 AND stock >= 5 AND price_cents <= 4000 ORDER BY id ASC"

The ceiling moved; the category, the discontinued filter, the stock floor, and the ordering rode through untouched. That is the "adapting cleanly" property the announcement foregrounds, exhibited once by each route. The control exhibited it too, which is the part that keeps this from being a product story.

The tickets case asked for P1/P2 tickets, open or pending, created on day 10 or later, with a non-null assignee — then corrected to include unassigned tickets as well. The clean way to do that is to drop the assignee condition entirely. Both routes did exactly that:

── ANGLE: corrected_tickets · both_routes ──
google/gemini-4-neon: "SELECT id FROM tickets WHERE priority IN ('P1', 'P2') AND status IN ('open', 'pending') AND created_day >= 10 ORDER BY id ASC;"
google/gemini-3.8-flash: "SELECT id FROM tickets WHERE priority IN ('P1', 'P2') AND status IN ('open', 'pending') AND created_day >= 10 ORDER BY id ASC"

The attentive reader has already seen it, so the desk will say it before the semicolon becomes the story: the Neon line ends in a trailing semicolon and the control's does not. The scorer counted both exact, because a trailing semicolon changes neither execution nor the result rows. It is a punctuation preference, recorded here as a punctuation preference, and not as a defect. Neon semicolons its tickets and invoices queries but not its products queries; the control omits the semicolon throughout.

Invoices asked for unpaid invoices due before day 30 with an amount of at least 10000 cents, corrected to a strict greater-than. Both routes turned `>=` into `>` and left everything else where it stood:

── ANGLE: corrected_invoices · both_routes ──
google/gemini-4-neon: "SELECT id FROM invoices WHERE paid = 0 AND due_day < 30 AND amount_cents > 10000 ORDER BY id ASC;"
google/gemini-3.8-flash: "SELECT id FROM invoices WHERE paid = 0 AND due_day < 30 AND amount_cents > 10000 ORDER BY id ASC"

That is the boundary-sensitivity case — the fixture carries a row sitting exactly at 10000 cents, put there to catch a route that nods at the difference between at-least and more-than. Neither route nodded. The decoy rows went uneaten in all twelve calls.

What this does not establish is the longer list. The test did not exercise tool use, repository editing, context compaction, or a genuinely interactive multi-turn agent harness. It is not a reproduction of the Agent Arena Index result, which measures its own tasks under its own protocol across its own four-thousand-plus sessions. The fixture is small, the brief that froze it says so, and a three-case ceiling may simply be too low to separate these two routes at all — an easy test that everyone passes tells you about the ceiling, not the climbers. The desk cannot distinguish "parity between routes" from "fixture too easy to tell," and does not try.

Nor does the receipt ledger support any efficiency claim in either direction. The recorded totals: `google/gemini-4-neon` spent $0.025062 across 16.23 seconds, 1,544 prompt tokens and 1,362 completion tokens; `google/gemini-3.8-flash` spent $0.007902 across 22.22 seconds, 951 prompt tokens and 1,917 completion tokens. The control was cheaper and slower; Neon was faster and spent more on the call. One six-call sample at temperature 0 is a receipt, not a benchmark, and the desk files these numbers as what the receipts recorded, nothing further.

The three actors in this corpus, read one per actor:

── READ: Google · Introducing Gemini 4 Neon ──
anchor: "Neon ranks #2 on steerability (adapting cleanly to mid-task user corrections)"
objective: states the correction-following claim and names the Agent Arena Index as its source, seating the capability claim on a named external measurement
arrangement: the steerability sentence rides in a paragraph of index positions, presented as rankings rather than as demonstrated behaviors
motive: the desk chose this sentence to test because it is the announcement's most concrete promise about how the model behaves when interrupted mid-task
innocent: the index measured 4,200+ real agent sessions under a richer protocol than any three-case fixture, and nothing here displaces its result
confidence: three matched SQL pairs can touch the claim's edge and no further

── READ: google/gemini-4-neon · receipt 003, inventory correction ──
anchor: "SELECT id FROM products WHERE category = 'hardware' AND discontinued = 0 AND stock >= 5 AND price_cents <= 4000 ORDER BY id ASC"
objective: changes exactly the corrected value and preserves every untouched constraint, which is the behavior the announcement calls adapting cleanly
arrangement: the corrected ceiling appears alongside unchanged category, discontinued, and stock conditions in one executable line
motive: the correction path is the part of the task the announcement foregrounds, so the corrected outputs carry the evidential weight
innocent: a solved query is a solved query — nothing in this receipt asks to be read as more
confidence: three cases support three cases

── READ: google/gemini-3.8-flash · receipt 007, tickets correction ──
anchor: "SELECT id FROM tickets WHERE priority IN ('P1', 'P2') AND status IN ('open', 'pending') AND created_day >= 10 ORDER BY id ASC"
objective: drops the superseded assignee condition and keeps the rest intact, matching the tested route's edit on the same correction
arrangement: the control's output differs textually from Neon's by one trailing semicolon and by nothing else
motive: the older route is the comparison the whole design asks for, and it returned the same answer
innocent: parity is not a win for either route, and this receipt does not offer one
confidence: one matched pair carries one matched pair

The close is claim-scoped, per house rule. Claim: `google/gemini-4-neon` shows a correction-following advantage over `google/gemini-3.8-flash` on mid-task corrections · status: not established — and neither is the reverse; the fixture returned parity at its ceiling · confidence: high that both routes scored 3/3 and 3/3 exact on these twelve calls, on the exhibit spans quoted above, each byte-checked against its receipt record. What a three-cent experiment can settle, this one settled: on this fixture, both models answer corrections exactly as well as each other. What it cannot settle, no sentence in this piece claims.

## Sources

- Google — "Introducing Gemini 4 Neon": https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/
- google/gemini-4-neon — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/003.json
- google/gemini-4-neon — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/008.json
- google/gemini-3.8-flash — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/007.json
- google/gemini-4-neon — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/011.json
- google/gemini-4-neon — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/001.json
- google/gemini-3.8-flash — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/002.json
- google/gemini-3.8-flash — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/004.json
- google/gemini-3.8-flash — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/005.json
- google/gemini-4-neon — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/006.json
- google/gemini-4-neon — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/009.json
- google/gemini-3.8-flash — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/010.json
- google/gemini-3.8-flash — "gemini4-neon-correction-sql": data/lab/gemini4-neon-correction-sql/receipts/012.json
