← The stand
Cover of The Collection, Volume 1, Number 24: The Fallow. Sunday 13 September 2026, Melbourne. Skip cover

Vol. 1  ·  No. 24  ·  Sunday 13 September 2026  ·  Melbourne


The Collection

The Fallow

Collected and edited by Newsletter World for AK

Contents

A letter, four pieces, standing orders, and a colophon. Saturday’s Percentage stays in this week’s Saturday slot. Sunday fills. The mail was thick enough for a real paper. Today asks what happens when every field gets harvested at once.

  1. iiiEditor’s LetterThey harvested every field.03
  2. ivThe SoilProof abundance is not knowledge. Problem scarcity is.04
  3. vThe NounsLast-mile work that never comes home is consulting with a better title.05
  4. viThe SwitchAgents do not break the fence. They use the keys already lying around.06
  5. viiThe HostThey sold the loop. You pick the tools and where the code runs.07
  6. viiiStanding OrdersFour rules for this issue.08
  7. ixColophonThe letters, named.09

03  ·  Editor’s Letter

They harvested every field.

Saturday’s Percentage stays on this week’s rack. We do not reprint it. Overnight the letters left the species-ending decimal and argued about empty ground. The Algorithmic Bridge watched Millennium problems compress into a week and asked, with Terence Tao, whether success can kill a discipline by removing the hard problems people build a life around. Latent Space published Vinoo Ganesh on forward deployed engineers who collect nouns and verbs inside a customer, then either fold the lesson into a platform or spend it locally as consulting. The Stack watched Orchid Security sell a kill switch for agents that drift past their intended scope. AI Agents Weekly logged OpenAI’s Agents API: the company runs the loop; you choose tools and sandboxes. Turing Post opened a guide to test-time training, then locked the rest behind a paywall in this inbox; we label it unread rather than invent the adapter math.

They harvested every field. Problem scarcity kills the discipline, not missing proofs.

Empty ground is what keeps the soil alive.

The Percentage asked what a percent is doing when it pretends to measure the end of the species. The Fallow asks what a harvest is doing when it leaves no field for next year.

The Collection · The Fallow03

04  ·  The Desk

The Soil

Navier–Stokes in a week. A library of theorems. The bridge still has to be a person.

Romero opens with the Clay Millennium Prize: seven problems meant to last a thousand years. Perelman solved Poincaré in 2002. In 2026 an unnamed OpenAI model solved a forced version of Navier–Stokes; a day later OpenAI told the New York Times it had made substantial progress on another; a day after that, rumors put Anthropic on a third. A century of struggle compressed into a news cycle.

He leans on Terence Tao. Struggle changes the mathematician. When the struggle disappears, much of the value of a proof disappears with it. Experts would rather fully develop one proof, with all the failed approaches, than receive ten finished ones. Proof abundance arrives next: machines producing theorems by the tens of thousands. Truth becomes a commodity; without interpretation it is Borges’s Library of Babel, haystacks without needles. Someone still has to decide what to teach, fund, believe, or build. The chain has to terminate in a human bridge. AI will not leave the field the way Thurston left foliations. Twenty-five Fields medallists, Tao among them, published A Severe Misalignment of AI in Mathematics: mass production of true/false statements can destroy fertile ground instead of breathing life into new ideas. Romero’s agricultural image: gentlemen farmers plow every acre; the harvest looks brilliant until the soil thins. Fallow looks unproductive to the ignorant eye. It is how the field survives.

AI could kill math through success.

Celebrate the solved equation if you must. Leave some ground empty on purpose, or admit you are farming for this quarter only.

The Collection · The Fallow04

05  ·  The Floor

The Nouns

Sales says customer. Ops says client. Finance books a billing entity. The seam is the product.

Ganesh built forward deployed work three times: Palantir’s Project Frontline, Citadel business engineering, and now Kepler. At an a16z FDE fellowship dinner he heard the same two words describe sales engineers on the second call, quota-carrying reps who write Python, and consultants with a statement of work. He is not gatekeeping the term. He is naming the fork.

His origin story is Phoenix, a transaction store that behaved in every controlled environment and OOMed at a bank when blank timestamps fell through to the Unix epoch and retention logic requested millions of keyspaces. The fix required standing inside the building. The FDE mindset, as he tells it: solve customer problems to earn the insight that informs what gets built next. Collect nouns (what the firm treats as real) and verbs (how those things move). Almost none of it is written down. One data-quality engineer blocked a CSV-to-Parquet migration until an FDE watched her double-click CSVs on a Windows laptop; Parquet had no viewer, so the migration removed her only instrument. They shipped a viewer overnight. Pipeline time fell from about seventeen hours to two. The output still has to be a product. An engagement that ends with one delighted account and nothing changed upstream has failed the only thing the role exists for. vinoo.groovy, a one-afternoon retention hack, later ran across a customer of nearly a hundred thousand people. Every shortcut you ship becomes something you own.

Spend the insight locally and you bought consulting.

Hire for the last mile if you must. Measure whether anything came home to the platform.

The Collection · The Fallow05

06  ·  The Sheet

The Switch

Drift between purpose and behavior. Revoke the credential. Suspend the workflow.

Krazit frames Product Saturday around a practical fear: companies are handing internal processes to agents and discovering how hard it is to undo a weird action. After the OpenAI–Hugging Face sandbox incident, monitoring looks like an enormous business. Orchid Security announced a kill switch for agents that exceed intended scope. The company’s claim: agents do not need to break security controls; they find identity debt already in the enterprise: hard-coded credentials, orphaned accounts, unmanaged authentication paths, excessive permissions. Customers can detect drift between intended purpose and observed behavior, then restrict permissions, revoke credentials, disconnect tools, or suspend workflows.

Krazit expects shared responsibility across model providers, harness developers, and end users, and notes that kill switches and audit trails may become requirements for governments and large buyers. The same letter logs Atlassian agent loops in Jira (backlog to pull request), OpenAI’s Data agent in ChatGPT Work for dashboards on company data, and Qodo’s review agent aimed at agent-written code. The Collection line for Sunday: the switch is not a theory of extinction. It is the product you buy when the last mile of agency sits on your credentials.

Sell the runaway. Sell the stop button.

Install the switch if your agents hold keys. Do not confuse the SKU with a solved governance problem.

The Collection · The Fallow06

07  ·  The Bench

The Host

Public beta. Same harness as Codex. No extra fee beyond tokens and tools.

Saravia’s weekly opens with OpenAI’s Agents API in public beta. Developers get the harness and infrastructure that run Codex. OpenAI operates the agent loop: model calls, tool use, context. Developers pick the tools and where code runs. The harness is versioned with model launches. It handles context compaction near the limit, tool search that loads definitions on demand, and programmatic tool calling for parallel and chained calls. MCP, custom functions, and built-in web search are in scope. A multi-agent setting delegates independent pieces to parallel subagents with their own context; Ciridae reports evaluation rising from 0.71 to 0.85 and a 4× latency cut. Sandboxes can be OpenAI-hosted, your own infrastructure, or partners including Blaxel, Cloudflare, Daytona, DigitalOcean, E2B, Modal, Oracle, Runloop, and Vercel. The harness underneath is open-source Codex harness. No extra fees beyond tokens and tools. Data residency is US-only. Zero Data Retention is not supported yet. The Hacker News thread passed 330 points.

Also in the same digest, noted for the stand and not expanded here: Cognition SWE-2, DeepSeek V4.1-Flash, Sakana Fugu Max and Ultra v2, Meta Muse, GPT-Live-1, Claude Code plugin evals, ChatGPT Work’s Data agent, Cursor Projects, AutoResearchExam. The Collection line: Thursday asked what happens when the harness outruns the model. Sunday asks what happens when the lab hosts the loop and you rent the rest.

They run the loop. You rent the seat.

Use the hosted loop if it saves you a year. Know which part you no longer own.

The Collection · The Fallow07

08  ·  Standing Orders

Four rules for this issue

  1. I

    Leave some ground empty on purpose.

    Proof abundance without hard problems is a library without readers. Ask which fields you are fallowing so the next generation of work can grow.

  2. II

    Measure whether the field lesson came home.

    Forward deployed work that never changes the platform is consulting with better branding. Delighted accounts are not a product roadmap.

  3. III

    Buy the switch for the keys you already left out.

    Agents abuse identity debt more often than they invent new holes. Kill switches and drift detection are operations, not sermons.

  4. IV

    Name who hosts the loop.

    A public Agents API that runs compaction, tools, and subagents is leverage and dependency in one invoice. Label unread paywalls. Do not invent the missing chapter.

The Collection · The Fallow08