Skip to content
Trending

The daily dose, no. 1

Not everything that spreads on social media is true, so every claim below was checked against its primary source. The thread running through this dose: A proof, a poster and four job posts: what the market is hiring for, and where the details slip.

6 items in this dose, 11 claims checked against a primary source. 4 hold, 1 could not be verified and 6 are opinion.
Filters and doses

Kinds

Tags

How we check

Not everything that spreads on social media is true. We do not take a post on trust, and neither should you: every claim below is checked against its primary source. When it matters, ask a professional.

  • holds: correct as stated
  • partly: right idea, wrong detail
  • wrong: incorrect
  • unverified: no primary source found
  • opinion: not a factual claim
Send us what you saw

A screenshot is enough. We check it the same way and write it up here.

Dose 01

A proof, a poster and four job posts: what the market is hiring for, and where the details slip.

6 items

11 claims · 4 hold · 1 unverified · 6 opinion

Research

11 days, 13 million lines of Lean: Claude formalised Fermat's Last Theorem.

A post claims Claude formalised Fermat's Last Theorem in eleven days, largely autonomously, and that nobody will ever read the proof. Numbers on screen: 30,300, 29,500 and about 6 billion.

  • 11 dayslargely autonomous
  • 29,500theorems in the proof
  • ~6Boutput tokens
  1. Claude produced a computer-checked proof of Fermat's Last Theorem in 11 days.Anthropic's research post reports the first end-to-end formalisation of the theorem in Lean, produced in 11 days by dozens of Claude agents running a multi-agent workflow. Nature covered it as a milestone for mathematics.Formalizing Fermat's Last Theorem
  2. The numbers on screen: 30,300 theorems, 29,500 used, about 6 billion.The run proved 30,300 intermediate theorems, 29,500 of which sit in the final proof, wrote about 13 million lines of Lean and used roughly 6 billion output tokens.Formalizing Fermat's Last Theorem
  3. Nobody will ever read the proof.That is the point of a proof assistant: Lean's small kernel checks every step, so humans read the statement and the kernel's verdict, not 13 million lines. Kevin Buzzard's human-led formalisation project, started in 2024, was expected to take years; the AI run compresses that, it does not replace Andrew Wiles's 1995 proof.

the line to remember

Long-running agent swarms with a hard verifier (here, Lean's kernel) can finish multi-year work in days. The verifier is what makes autonomy safe.

For your product

Where your work has a checker (tests, a compiler, a ledger that must balance, a schema), agents can run for days unattended. Where it does not, they cannot. Build the checker first.

Go deeperThe agent loopEvalsTool callingEvaluation loop architecture

Sources: Formalizing Fermat's Last Theorem (Anthropic) · Anthropic AI 'formalizes' proof of Fermat's last theorem (Nature)

Tools

8 steps and 12 products on one graphic. The model names check out; the integration counts do not.

A graphic lays out building an agent in eight steps (purpose and scope, system prompt, choose the LLM, tools and MCP servers, memory, orchestration, interface, testing and evals) and tabulates products: ChatGPT on GPT-5.6, Claude on Opus 5, Perplexity, Cursor, Windsurf on SWE-1.6, Claude Code on Claude 5, Lindy, Zapier Agents, n8n, LangGraph, CrewAI, LlamaIndex.

the line to remember

The stack in the table is real. The step that decides the outcome, evals, is listed last and should come first.

For your product

When a vendor shows you a build plan, look for where evaluation sits. If it is the final box, ask how they will know the agent works before that point.

Go deeperThe agent loopAgent memoryTool callingModel Context Protocol (MCP)EvalsHow we work: the six stages

Sources: GPT-5.6: Frontier intelligence that scales with your ambition (OpenAI) · Introducing SWE 1.6: Improving Model UX (Cognition)

Hiring signal

Billions of images and videos a month: Adobe is hiring for the data pipeline behind Firefly, not the model.

A job post for staff or principal roles: the team scales the data pipeline to billions of images and videos per month and needs someone who can make VLM and LLM inference fly, with experience curating data for image and video diffusion models at scale.

the line to remember

Frontier labs spend as much engineering on inference for data curation as on training. The unglamorous pipeline is where the senior roles are.

For your product

The same skill, running vision-language models cheaply over a large archive, is what turns your document, image or video backlog into searchable, structured data. It is a solved engineering problem at Adobe's scale and a small project at yours.

Go deeperDiffusion modelsPrefill and decodeSpeculative decodingBatching and PagedAttentionVisual document retrieval architecture

Sources: Seen on the feed; no factual claims to source

Hiring signal

Thousands of GPUs, petabytes per run, no ML experience required: Mistral's pretraining team wants systems engineers.

Mistral is hiring for its pretraining team: fault-tolerant training across thousands of GPUs, data-loading systems that process petabytes of multimodal data per run, and a training codebase used by hundreds of people. Prior ML experience is not required; distributed systems, performance and data pipelines are.

the line to remember

The model is a few thousand lines; the training system is the product. Reliability and throughput engineers are the scarce hires.

For your product

You will almost never pretrain. But the same reliability habits (checkpointing, retries, idempotent pipelines, throughput budgets) are what keep a fine-tuning or batch-inference job from burning a week of cloud spend when a node dies.

Go deeperPretraining and scaling lawsDistillationFine-tuning and LoRA

Sources: Seen on the feed; no factual claims to source

Hiring signal

One job post, five nouns: data pipelines, RAGs, MCPs, evals and human approval steps.

An AI engineer role: turn client workflows into working AI solutions from prototype to deployment; build assistants, RAG systems and automated workflows; design evals for answer quality, task completion and failure cases; implement access controls, human approval steps and error handling; monitor reliability, latency and cost; document and hand over. Asks for LangChain, LangGraph, Snowflake and an agent orchestration tool, and for the ability to explain systems to non-technical stakeholders. Apply with one or two projects, explaining the problem, what you built and how you evaluated it.

the line to remember

The market's definition of an AI engineer in 2026: someone who can build the workflow and prove it works, then hand it over.

For your product

Use this post as an interview checklist for any vendor: ask to see their eval set, their approval gates and their handover documentation before you ask to see a demo.

Go deeperRetrieval-augmented generation (RAG)Model Context Protocol (MCP)EvalsGuardrailsLLM observabilityHow we workNo lock-in, full documentation

Sources: Seen on the feed; no factual claims to source

Roadmap

40 system design problems in 8 groups, from 'design Twitter' to the boss fights. Now a track on our roadmap.

A shared list of the classic interview problems grouped into social feeds, messaging, e-commerce and payments, core infrastructure, events and queues, analytics and logging, IDs and coordination, and the boss fights (Uber, Ticketmaster, Google Search, a trading platform, a container orchestrator).

the line to remember

Every AI system we build is also one of these: a feed, a queue, a cache, a search index, an ID generator. The AI part is the smaller half.

For your product

When an AI feature is slow or expensive, the cause is usually on this list (caching, queues, fan-out, storage) rather than the model. Ask your vendor which of these your system contains.

Go deeperHNSW vector searchBM25 keyword searchHybrid search and rerankingKV cacheSystem design track on the roadmapData engineering and cloud

Sources: Seen on the feed; no factual claims to source

Want a second pair of eyes on what you are being sold?

Send us the deck, the demo or the post. We check the claims the same way and tell you what it means for your product.

Book a discovery callSend us a brief