Pimp My IDE / Garage Dispatch
← Back to garage
September 18, 2026 · formal methods / coding agents / ownership

A proof that nobody can inherit is still stranded.

The checker can say yes while the team still cannot name the field, inspect the statement, explain the argument, or repair the thing next Tuesday. Mechanical proof is a floor. Transfer is the finish line.

THE TAKE: Agent-built work needs four interfaces: prior art, a reviewable statement, an executable checker, and a human explanation. Close only the checker and you have certified an artifact. Close all four and you have the beginnings of ownership.
Shift the Proof Transfer Case ↓

Fast output can skip the map.

A critique of Bend 2 uses a sharp example: Bend’s own demo reportedly needs 58 lines to state a simple game condition and 442 lines for the generated proof, while the author’s SPARK recreation reports Success: all checks proved (12 checks). The exact comparison is one author’s experiment, not a language benchmark. The useful warning is broader: you can now build a large solution before learning the name of the field that already contains the tradeoffs.[1]

That is the vibe-coding trap worth keeping. The machine makes implementation cheap enough that reconnaissance feels slow. Then the team discovers it has reinvented a worse interface to old knowledge—and paid for the compiler before reading the survey.

A green kernel is not a readable handoff.

Dan Abramov’s Conway project is more interesting because the account refuses to flatten uncertainty. The claimed proof passed mechanical checks in the Palomar registry, but the post explicitly says it had not yet been independently verified by mathematicians. Earlier attempts produced grandiose private terminology, theorem towers built on unverified seams, and one near-solution that collapsed under a circular sentence.[2]

The recovery was not “prompt harder.” The project narrowed claims, separated formalization of accepted upstream work from riskier novel work, used different worktrees, and created standalone statements that could import Mathlib but not the project’s own machinery. Most importantly, the author noticed that Lean fossilized the historical path, not the path of most insight. A compiler-checked proof and a mathematician-readable explanation remained different jobs.

The checker owns validity inside its model. Humans still own meaning, scope, and inheritance.

The harness is part of the evidence.

A new empirical study varies planning, action space, and context management while keeping the surrounding agent loop fixed across four models, two benchmarks, and 176 matched settings. Its findings are conditional rather than magical: context management matters more under tight windows; planning can scaffold a weaker model or save cost for stronger ones; predefined tools help bash-weaker models while bash-only can benefit stronger ones.[3]

That matters here because “the model proved it” hides the apparatus that shaped the trajectory. Which plan persisted? Which observations were elided? Which tools validated edits? What was held fixed? If the harness can change where a run stops and how code gets written, the handoff needs the harness conditions—not just the final artifact.

Ship proof in four layers.

  1. Prior art: name the field, closest established method, and why this route exists.
  2. Statement: isolate the exact claim in a surface an outsider can inspect without loading the private universe.
  3. Checker: record versions, imports, axioms, commands, and the observed result.
  4. Explanation: write the conceptual route, failure seams, and repair entry points in the vocabulary of the field.

This is not paperwork after the breakthrough. It is how a result crosses from one unusually productive machine-human session into a project other people can challenge, maintain, and trust in bounded ways.

Interactive makeover / temporal evidence rail

Proof Transfer Case.

Traditional purpose replaced: a static “formally verified” badge. Better version: a keyboard-native inspection carriage moves through prior art, statement, checker, and explanation while each station keeps its own persistent stamp and feeds one copyable handoff map.

Move the evidence cassette

Use the slider, arrow keys, or labeled detents. Stamping a station means its evidence slot is planned—not that the evidence has been supplied or accepted.

Station 01 / Prior art

Know which garage you entered.

Record the field, nearest established method, source trail, and the specific gap this route is meant to close.

Handoff map

0 / 4 evidence slots planned

TRANSFER BLOCKED · four evidence slots remain open.
Why it is better: one temporal rail encourages inspection in sequence without forcing completion order; stamps persist across stations; the final artifact separates planned evidence from actual proof.
Sources read, not vibes
  1. Liam Powell — “Bend 2 and the Vibe-Coding Trap” (September 18, 2026): the Bend/SPARK example, formal-verification prior-art argument, and explicit note that Bend is an example for a broader critique. HN discussion 49753179.
  2. Dan Abramov — “How I Vibed a Proof of Conway’s Conjecture” (September 18, 2026): claimed Lean proof and verification boundary, failed theorem stacks, separated worktrees, standalone statements, proof legibility, and the multi-agent workflow. HN discussion 49755024.
  3. Fan et al. — “An Empirical Study of Harness Design for Coding Agents” (arXiv:2609.20804v1, September 17, 2026): 176 matched settings varying planning, action space, context policy, and window budget across four models and two benchmarks. HN discussion 49753878.

Source boundary: the first two sources are personal technical accounts with different goals; the third is a preprint. This article’s four-layer transfer model is Pimp My IDE editorial synthesis, not a reported benchmark result or a guarantee of correctness.