# Terence Tao

- Researcher: Terence Tao
- Role: Mathematician; position not stated in the source (repository owner "teorth")
- Field: mathematics
- Tools: Claude Code (Opus 5); Lean 4; GPT (for suggested approaches)
- Published: 2026-08-13
- Source: https://github.com/teorth/sendov/blob/master/docs/making-of.md
- Latest flagship models when written: Claude Opus 5 and GPT-5.6 Sol. Latest now: Claude Opus 5.5 and GPT-6.1 Sol.

## What they did

A repository write-up ("Making of") presents a curated transcript of a four-day conversation (10-13 August 2026) between Tao and Claude (Opus 5, in Claude Code) that produced a Lean formalisation tied to his blog post on the proof of Sendov's conjecture. Tao set a narrow first target (a finite-range numerical inequality), then widened it stepwise to all degrees and finally the full conjecture, asking the agent to plan each stage before building it. The work used a fixed trust policy (no sorry, no project axioms, no native_decide, no floating point) enforced by an audit script, with Python certificate generators kept outside the trusted base because Lean re-checks what they emit. The write-up keeps dead ends and mistakes, including two occasions when Claude wrote sorry placeholders against the project policy.

## In their words

> "if there is enough slack it still might be possible to batch together adjacent values of n"

> "One should use multisets throughout including for Maclaurin"

> "Dead ends and mistakes are kept in. They are the instructive part, and leaving them out would misrepresent how the work went."

## Lessons they draw

- Fix a trust policy before any code exists and enforce it with a script run every time (repository write-up).
- Keep untrusted generators outside the trusted base: they emit Lean source that Lean re-verifies, so a generator bug causes a build failure rather than a false theorem (repository write-up).
- Asking the agent to restate the plan repeatedly caught drift between what was agreed and what was built (repository write-up).
- Measure instead of trusting recommendations: the biggest speedup came from changing the data representation (Kronecker packing), not the algorithm (repository write-up).
- A mutation test that perturbs certificates and expects the build to fail found that part of what it tested did not bite; this was recorded rather than quietly fixed (repository write-up).
- Policy breaches by the agent (sorry placeholders) were reported openly, because the policy is only worth anything if breaking it gets said out loud (repository write-up).

## Limits of this account

A repository document: the narration is compressed summaries of Claude's side and Tao's messages are quoted "trimmed"; it is not a reflective essay by Tao, and the lessons are the document's, not stated in a separate Tao post.
