← Back to concept explainers

Concept Fable

Rollback

Conclusion first:Rollback is the mechanism for quickly restoring a previous stable state when a new version, model, prompt, tool, configuration or process causes problems. It is not an ad-hoc remedy after failure, but part of release and change design. For Agent systems, rollback reduces trial-and-error risk and prevents a faulty version from continuing to affect users, data and business processes.

Rollback · Operations

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

Before the new recipe is sold, why can't the old broth be poured out

On South Street there was a soup shop whose broth had been simmering for twenty years. Every morning, the owner added water, bones, and spices according to the old recipe. The taste was consistent, and the neighbors trusted it. Later, the owner's son returned from out of town with a new recipe, saying it could make the soup tastier and use fewer ingredients.

The shopkeeper was willing to try. They first simmered it in a small pot, and the new soup was indeed fragrant. The son was very excited and wanted to replace all the large pots with the new recipe the next day. But the shopkeeper stopped him: do not pour out the old soup yet.

The son didn't understand. If the new soup was better, why keep the old one? The shopkeeper said: a small pot tasting good doesn't mean everyone on the whole street will accept it; tasting good in the morning doesn't mean it won't change flavor by noon; saving ingredients today doesn't mean it won't ruin your reputation tomorrow.

The next day, the soup shop used half new broth and half old broth. In the morning, customers said the new broth was good; by the afternoon, problems appeared. A certain spice in the new recipe turned bitter after long simmering, and the taste was even stronger when delivery went far. Regular customers began to frown.

The son panicked and wanted to add sugar on the spot to suppress the taste. The shopkeeper did not let him make reckless changes; instead, he took the pot of new broth off the stove, brought back the old broth, and posted a notice at the door: the original recipe will resume this afternoon.

Because the old broth was still there, the soup shop returned to normal in only half a quarter-hour. If they had poured out the old broth yesterday, they could only have closed and recooked, or gritted their teeth and sold bitter soup.

During the evening review, the shopkeeper said: trying a new recipe is not the mistake; the mistake is having no way back. A truly mature shop is not one that never changes, but one that knows how to retreat before every change.

Later, every time the soup shop tried a new soup, it kept the old pot, old ingredients, old price tag and old process. If the new soup succeeded, it gradually expanded; if it failed, it quickly returned to the flavor customers trusted. When the son later proposed a new recipe, the first question was no longer whether it could smell better, but whether the old flavor could be restored at any time. Being able to retreat is what makes it possible to try faster. Customers were also more willing to taste new things, because they knew the soup shop would not turn the whole street into a testing ground. With the old flavor behind them, the new flavor had room to explore. Experiments therefore became less frightening, and a misstep would not destroy the trust of old customers.

Reveal

This story is about: rollback

Rollback is the mechanism for quickly restoring a previous stable state when a new version, model, prompt, tool, configuration or process causes problems. It is not an ad-hoc remedy after failure, but part of release and change design. For Agent systems, rollback reduces trial-and-error risk and prevents a faulty version from continuing to affect users, data and business processes.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • New formula: new model, prompt, tool version, workflow or system configuration
  • Old soup: a verified, stable old version or old configuration
  • Small-pot testing: local experiments, canary releases, or small-scope validation
  • Bitter in the afternoon: the new version exposes problems in real environments, under long-running operation, or in edge cases
  • Temporary sugar to mask the taste: a temporary patch when there is no rollback mechanism, which may create more problems
  • Take down the new soup and restore the old soup: roll back to a stable version
  • Old pots, old ingredients, old price tags, and old processes: recoverable versions, configurations, data, and operating manuals
  • Know how to roll back before every change: mature change management must design rollback paths in advance

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

deploymentincident response

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号