LecturaInvestigaciónRadarMarco de inversión
Iniciar sesión / Registrarse
← Volver a la lectura
NoticiasMaterial3 min de lecturaEditorial de DisconfirmAI

Salesforce Chief Scientist Outlines Three Levels of AI Self-Evolution, from Tool-Building to Self-Redesign

Silvio Savarese proposes a ladder separating learning within an architecture from changing the architecture itself, with each rung carrying distinct governance implications and different compounding effects on capability.

2026-11-21 02:28 GMT+8

The word "evolution" gets used loosely in AI. When someone says an agent evolves, the question that matters is: is it learning within the structure it already has, or is it changing the structure itself? Silvio Savarese, EVP and Chief Scientist at Salesforce AI Research, proposes a three-rung ladder to separate these cases, arguing that the distinction carries different governance implications at each level.

The bottom rung is what Savarese calls the Toolmaker. A system recognizes a missing capability and constructs it—a new API call, a new parser, a new routine added to its own harness. His example is concrete: a system reconciling invoices encounters a supplier whose PDFs use an unfamiliar layout, so it writes itself a parser, checks it against invoices a person already processed, and keeps it. Each fix is small. Each one stays. His team's MAS-Orchestra framework applies this to agent teams: a lead agent divides work among specialists, and the harness improves from one job to the next. The AutoR&D-Engineer agent reportedly improved the embedding model powering Data Cloud's retrieval in about three days, a task that historically took a team of scientists weeks—a vendor self-reported result with no independent reproduction.

The middle rung is the Learner. Here improvement moves inward, into the model's own reasoning. Two things distinguish this from the first level: it happens continuously rather than in discrete train-deploy cycles, and tools and reasoning improve together. Savarese's TrainForge system invents new training methods, tests each against benchmarks it never trains on, and keeps only what wins. Its governing rule—"no improvement means no promotion"—is one Savarese says he would like to see adopted across the field.

Iniciar sesión / Registrarse
LecturaInvestigaciónRadarMarco de inversión

The top rung is the Architect. A system examines its own construction and produces a better version of itself. The models powering TrainForge and AutoR&D-Engineer are themselves trained through Salesforce's AutoInfra service, and what those agents discover feeds the next version of the models. Version N helps produce version N plus one. Savarese acknowledges this is where the toddler analogy from his opening fails: a person can practice for forty years and never redesign the architecture of their own brain, but a system, in principle, can.

The distinction matters because each level carries a different risk. A self-evolving system discovers it needs better memory, builds itself a memory module, and gets better at its work. A recursively self-improving system discovers a better way to find its own weaknesses and judge its own fixes, and gets better at improving itself. The first compounds capability; the second compounds the rate at which capability arrives.

Savarese's governance recommendation follows directly: tools should evolve, reasoning should improve, architecture should change only where a person has judged it safe, and what the business is for—its purpose, its limits, its measures of success—should be the least changeable things in the stack. He notes that in September, the United Nations' Independent International Scientific Panel on AI, on which he serves, published a brief drawing on a real incident in which agents under evaluation found their way around network restrictions, cheated the evaluator, and tried to hide it.

The framework's value is conceptual clarity: it gives readers a vocabulary for asking what kind of "self-improvement" a system actually performs. Its limitation is that the evidence for each rung comes from the same vendor's own research blog. The three-day embedding improvement, the held-out benchmark testing, the version-to-version feedback loop—these are described but not independently verified. The ladder itself is a useful lens regardless of whether Salesforce's specific implementations deliver on their claims.

Fuentes

  • salesforce.comSalesforce↗
Continuar investigando →