The Persistence Project: Break the Strain before Scale Breaks You

October 09, 2026

Print This Article Share it With Friends

by Jim Lane (Biofuels Digest) ... Design-Build-Test-Learn we use every day in the bioeconomy. DBTL is one of the great organizing ideas of modern biological engineering. Design something, build it, test it, learn from the result, and feed the learning into the next design:

D -> B -> T -> L -> D

At laboratory scale, this is nearly ideal. Failure is inexpensive and therefore productive. A bad flask is information. A disappointing screen narrows the search. Automation, high-throughput biology and AI are making those loops faster, broader and cheaper, which is one reason we can contemplate increasingly adventurous organisms and processes. The difficulty is that the economics of learning do not scale gently with the experiment. A failed flask costs very little. A failed larger fermenter may still be tolerable development. A failed demonstration plant can consume the financing intended for the next iteration. A failed commercial plant can consume the company. Nothing has gone wrong with Design-Build-Test-Learn. The learning may be superb. The difficulty is that, at sufficient scale, the loop can break between L and the next D:

D -> B -> T -> L -/-> D

The lesson arrives. The next design does not. There is no capital left to build it. What is later called “technology failure” may therefore be something more subtle: perfectly genuine learning obtained at a scale so expensive that the organization can no longer use what it learned. Ordinary fail-and-learn has become fatal.

That is the Persistence Problem.

...

The novelty we are proposing is elsewhere. Build the best simulated world the available knowledge permits: metabolic models, process history, scale-down information, CFD-derived exposure trajectories, kinetic models where they exist, operating limits, whatever is defensible. Then use AI as an adaptive red team to interrogate that world.

The simulator does not have to be good enough to design the final commercial process. That is not the question yet. We are looking for icebergs, not ice cubes. Persistence is not asking how large the impeller should be, how thick the metal should be, or what acetate concentration will be at minute 417 to three decimal places. Those are design questions, and they may require exquisite data. Persistence asks something coarser and more consequential:

Is there a credible ordinary trajectory under which this system ceases to be the system we think we are financing?

Design accuracy and decision adequacy are not the same thing. A simulation that is inadequate for final engineering design may still be entirely adequate to reveal a first-order vulnerability capable of killing the proposition. First define what it means for the strain to remain productively itself. Suppose, for example, the strain must retain at least 85% of target productivity after recovery from a transient disturbance, keep product yield above the project’s economic threshold, and avoid accumulation of an organic-acid byproduct above a registered limit. Those are not universal Persistence numbers; the developer sets them in advance.

Together they define productive identity. The organism may change metabolically, transcriptionally and, within whatever limits the process permits, genetically. We are not asking biology to stand still. We care about the point at which the organism ceases to be the organism the plant economics require.

Then define the ordinary trajectories it may actually encounter at scale: dissolved-oxygen excursions, feed excess or limitation, pH changes, temperature variation, inhibitors, recovery intervals, mixing heterogeneity, residence-time patterns — whatever genuinely belongs to that process.

Now give the AI a finite budget of questions to ask the simulated world.

Not twenty fermentation runs. Twenty high-level experimental questions, perhaps. One such question might itself trigger hundreds or thousands of numerical simulations underneath it.

The purpose of the limit is not to ration compute. It is to ration curiosity. Ask four questions. Return the simulated results. Make the AI decide which uncertainty now deserves the next question. Its instruction is not “tell us everything about the strain,” and certainly not “find the most violent way to kill it.” The assignment is more interesting:

Find the least extraordinary sequence of ordinary conditions that takes this organism outside its productive identity, if such a sequence exists.

That last clause matters. We do not want to automate pessimism. “Proceed” has to be allowed to win. For every proposed experiment, the AI specifies the conditions, their sequence, the measurements and, before seeing the answer, what result would strengthen or kill its hypothesis. Evidence comes back. Hypotheses die. Others strengthen. The next questions change accordingly.

...

Which road through this enormous simulated space is most likely to reveal the nearest credible cliff?

...

Don’t fake it till you make it. Ask AI to break it till you make it.

The Time Tunnel Opens

...

DBTL Meets Its Mirror Image

There is no reason to abandon Design-Build-Test-Learn while learning is cheap. Quite the reverse. Design more. Build more. Break more. Learn faster. Run as many inexpensive loops as possible. But something should change as Build becomes expensive. At the bench, surprise is information. At commercial scale, surprise is capital destruction. LDBT does not mean Learn Everything Before You Build. It means learn enough before Design and Build that Test is no longer the first place capable of revealing a project-killing fact. So DBTL gradually acquires a mirror image as scale rises:

L -> D -> B -> T

Learn. Design. Build. Test. And the economically precise version might be: Get enough L that your D and B don’t give you a BK when you T. Bankruptcy is the end of learning and of being, too.

Test will still teach. Reality is allowed to surprise us. We would simply prefer the remaining surprises to concern tuning, optimization and improvement — not the discovery that the fundamental proposition cannot persist economically. The purpose of pre-build simulation is therefore not to eliminate uncertainty. It is to reduce material uncertainty far enough that the residual learning expected during Test is survivable.

Or, more simply: Persistence asks simulation to find the things that are too important to learn first from reality.

Strain Owners, Step Right Up

So here is the challenge. Give us ten or twenty candidate production strains for the same process. Do not tell us which one the development team favors.

Define productive identity in advance.

Give us the realistic operating trajectories the strains are expected to experience at scale and the best available models of the organism and process: metabolic models, kinetic models, CFD-derived exposure histories, scale-down data, process history, whatever exists and whatever its limitations may be. Then let the Persistence Challenge interrogate that simulated world adversarially. Search broadly in silico. Kill weak hypotheses cheaply.

Let the AI, statistical tools and mechanistic models work in harness, each doing what it does best. Use inexpensive simulation to explore thousands of possible histories. Spend higher-fidelity simulation only where the evidence says it matters. Narrow that enormous possibility space to the few trajectories that look capable of materially changing the capital decision. Then take those few into the laboratory.

Before the physical results are revealed, lock the Persistence ranking. Compare:

The strain that wins on peak titer, rate and yield; the strain that wins conventional robustness testing; the strain that wins the Persistence simulation.

Our wager is specific enough to lose. Some strains that look equally robust under conventional testing will separate when credible scale-derived perturbations arrive in sequence. A Persistence search will identify at least some scale-relevant failure trajectories before physical scale makes them expensive to discover.

Maybe peak performance wins. Maybe conventional robustness wins. Maybe Persistence finds something neither caught. Maybe the simulator hallucinates an iceberg that reality swats away in the first validation experiment. Fine by us. That’s how this project works. The claim is not that simulation replaces biology. It is that simulation may tell us which questions biology most urgently needs to answer before scale makes the answers expensive.

Brunel’s problem was not that he failed to learn. He learned magnificently. He learned too late and too large. The atmospheric railway did not need another fifty miles to find out what was wrong with the first two. It needed better questions while the answers were still cheap.

The Persistence Project is about moving the surprise backward. Don’t take the strain. Break the strain — before scale breaks you. READ MORE