← Back to Concept Contrast

Concept Contrast Fable

Agents and Runtime

Conclusion first:One is the worker, and the other is the venue that lets the worker show up reliably for work. Confusing an Agent with a Runtime is like counting the actor and the theater as one expense.

One is the worker, and the other is the venue that lets the worker show up reliably for work. Confusing an Agent with a Runtime is like counting the actor and the theater as one expense.

Fable

The actor's and the theater's ledgers

In a theater there are famous performers, but also backstage staff managing lights, sets, ticket checking and scene changes. The manager oversees two seemingly similar operations: one is the people who sing and act on stage, the other is keeping the whole show running on time, safely and without interruptions. A new hand found it troublesome and merged the two ledgers into one, thinking both were related to success or failure anyway.

At first no one objected. The audience praised only the famous performers, so the apprentices assumed that hiring good performers would be enough to run ten consecutive days, and when the shopkeeper saw fewer pages, he even praised them for saving trouble. But when peak season arrived, the old accounts suddenly could not be explained clearly: whether the previous stall had not finished or the next stall had not held the line, no one could answer.

They first added more seals and slogans and required everyone to write in more detail. As a result, the booklet grew thicker and disputes increased. When something went wrong, everyone could find a sentence to excuse themselves, but no one knew which end to save first.

The old steward called everyone into the courtyard and had them retrace the actual course of events. Whatever concerned the immediate action went into the first book; whatever concerned subsequent responsibility went into the second. The two books referenced each other, but were no longer mixed onto the same page.

On the third night the light rope broke, props were misplaced, and no one notified the understudy; even the star performer couldn't save the show. After the split, many old conclusions changed: some work looked busy but hadn't actually blocked trouble; some arrangements were unremarkable in normal times yet preserved the whole in disaster.

To prevent newcomers from mixing things up again, the old steward had them each handle a small case. Only when the two ledgers could each answer their own questions and also connect with each other at the boundary would the small case pass. If someone still wrote the two matters on one page, they had to return to the scene and look again at who acted first and who was ultimately responsible; when it was unclear, it was better to ask once more than let a muddled account stay overnight; because on the day something truly went wrong, one missing line of distinction would make an extra team work in vain.

The garden owner trained stage skills and backstage rules separately: who could perform which act, who could open which door, and how to fall back when a scene went wrong were all written clearly. Later, when newcomers entered the trade, the old steward had them remember just one line: the skilled perform, while the venue that supports the skill handles boundaries, scheduling, and endurance.

Agent

A capability unit for executing specific tasks, completing one or more rounds of interaction through models, tools, prompts, and memory. Its value is reflected in "how well this task is done."

Runtime

The underlying environment that carries an Agent's long-term operation, responsible for scheduling, channel connections, permission management, state persistence and error recovery. Its value is shown in "whether all Agents can keep running stably."

Story Mapping

  • Actor: Agent, the capability carrier that completes specific tasks.
  • Theater venue (distribution box, ticketing system, dressing rooms): Runtime, providing the infrastructure and services needed to run.
  • Actor compensation: the Agent's direct costs (model calls, tool execution).
  • Site maintenance fee: the Runtime's platform costs (channels, scheduling, persistence, security).
  • The show trips a breaker: a Runtime failure leaves all Agents unable to work.

In the project

When evaluating an Agent solution, keep the two accounts separate. The Agent layer concerns model choice, tool integration and prompt effectiveness. The Runtime layer concerns channel stability, task scheduling, state recovery and permission boundaries. A common pitfall is attributing problems caused by a missing Runtime to poor Agent design—frequent Agent timeouts may not be due to badly written prompts, but to the scheduling layer lacking retry and fallback mechanisms.

京ICP备2026014272号