← Back to concept explainers

Concept Fable

Evaluation

Conclusion first:Evaluation uses human, rule-based, or model judges to measure an AI system's performance on task quality, safety, stability, and cost. Enterprise Agent evals should cover real tasks, edge cases, regression samples, safety red lines, latency, and cost, and be tied to the release process. Without evaluation, model upgrades, prompt changes, RAG adjustments, and tool modifications can only be judged by feel.

Evaluation, Evals · LLMOps / quality

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

Fable

All three masters say this ruler is the fairest

Tongqiao Town had three umbrella repair shops. Before the rainy season, the town mayor wanted to choose one to repair umbrellas for the whole town. All three masters brought out sample umbrellas, saying their own umbrellas were stronger, lighter and better looking.

The mayor initially had everyone demonstrate on the spot. The first umbrella was good in light rain, the second was steadier in strong wind, and the third opened and closed fastest. The onlookers grew more and more excited, but no one knew who to choose.

The assistant's naive patch was to have each craftsman score the others. As a result, they all picked the other's weakest weather to test, and also explained away exceptions for their own umbrellas. The score sheet was full, but the conclusions were more confused.

After the first batch of umbrellas was distributed, problems surfaced. The elderly found opening the umbrellas laborious, the boatmen said they flipped in sea winds, and schoolchildren found the umbrella fabric stained their schoolbags. The shop won on stage but lost on real streets.

So the mayor stopped the debate and first wrote down clearly which people the umbrella should serve, which weather, which failures were unacceptable, and which metrics were only reference. He collected the most common rainy-day scenarios from the past three years and invited different groups to try it out.

The new evaluation no longer looks at just one performance. It has fixed samples, human judgment, durability testing, cost records and failure classification. Every time the umbrella is changed, the same set of scenarios must be run to see whether it has improved, regressed, or only gotten better in one corner.

Later, all three shops could participate, but they could not come with stories alone. They had to bring data, error cases, boundary explanations, and revision comparisons. The mayor no longer asked "which umbrella is the smartest," but "which umbrella is the most reliable in the scenarios we need."

The townspeople discovered that the ruler itself also needed maintenance. New streets, new groups of people, and new rainy seasons would all make the old tests insufficient, so the evaluation set had to be continuously updated. The mayor finally understood that evaluation was not meant to prove that a certain umbrella was perfect, but to make every choice and change have a reviewable basis. Later, before changing umbrellas, the mayor first asked: does this ruler still represent today’s streets? If night markets had appeared on the street and the wind on the bridge was stronger, the old tests needed new scenarios. They also began keeping failure samples. Why a certain umbrella flipped, on which street it flipped, and who was holding it when it flipped told the craftsmen more about what to change in the next version than the winning sample umbrella did.

Reveal

This story is about: evaluation

Evaluation uses human, rule-based, or model judges to measure an AI system's performance on task quality, safety, stability, and cost. Enterprise Agent evals should cover real tasks, edge cases, regression samples, safety red lines, latency, and cost, and be tied to the release process. Without evaluation, model upgrades, prompt changes, RAG adjustments, and tool modifications can only be judged by feel.

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

  • Three umbrella repair shops: different models, prompts, RAG configurations, or Agent solutions
  • Live demonstration: demo and temporary manual experience
  • Scoring each other: uncontrolled, inconsistent subjective evaluation
  • Real-street failures: production scenarios expose boundary issues
  • Fixed rainy-day scenarios: golden set, benchmark and regression cases
  • Human judgment and failure classification: human evaluation, rubric, and error taxonomy
  • Rerun every time the umbrella changes: eval gate in CI/CD
  • Final insight: evals provide reviewable quality evidence for AI changes

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.

Benchmarkgolden setregression testLLM-as-judgehuman evaluationred teaming

Related distinctions

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

京ICP备2026014272号