← Back to concept explainers

Concept Fable

Action

Conclusion first:An action is a discrete operation an Agent performs in the environment, usually through tools, functions, APIs, browsers, or GUI automation. It differs from an ordinary text response: an action changes the state of an external system, such as sending an email, modifying a record, creating an order, submitting a form, or calling a payment interface. Enterprise Agents must treat actions as authorizable, verifiable, idempotent, and auditable execution units, rather than equating model output directly with a completed business operation.

Action · Agent capability

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

Fable

Every seal stamped weighs more than a verbal promise

The Jinshui County office received many requests every day. Some asked how to replace a land deed, some asked how to issue a tax receipt, some asked whether a shop could change its name. The clerks answered quickly and the villagers were satisfied, because most of the time it was just a question of how things were done.

The trouble began on the day the county office started handling things on behalf of others. A merchant said, since the clerk knows the process, why not directly help me stamp the seal, amend the register, and issue the notice. The clerk thought it was just a small favor, so he did it a few times.

Soon, problems came. Once, a shop changed its name without checking the mortgage, and the creditor came knocking; once, a tax receipt was reissued without voiding the old one, and two vouchers appeared in the accounts; another time, a clerk stamped a draft as an official document. The magistrate first ordered: from now on, think three times before answering. The clerks did become more cautious, but they still could not tell which things were merely suggestions and which, once done, would change the county's real records.

The advisor split actions into two categories: statements and seals. Statements can explain, compare, and remind; seals change ledgers, post notices, establish new contracts, change granary tags, and swap transit passes. Every seal must have an object, a matter, an authority, and a receipt.

He also decreed that boundaries must be checked before stamping. Minor matters could be handled by clerks, major matters required the magistrate's approval; the same tax receipt could not be reissued repeatedly; and if no reply had been received, check the stamp ledger first rather than stamping again immediately.

At first the county magistrate added only a verbal reminder: think clearly before acting on someone's behalf. But when things got busy no one thought, and the clerks casually turned "query the deed" into "rename and transfer ownership," and "ask about the tax rate" into "submit the tax receipt." A sentence turned from an answer into an action, and the consequences landed on the real ledgers.

Later the county office divided affairs into two categories. Explanations, inquiries, and listing steps could be answered directly; sealing, payment, altering registers, and issuing notices required checking identity, asking for confirmation, keeping evidence, and when necessary handing them to someone with a seal. The clerk finally understood that there is a threshold between explaining and acting, and crossing it means bearing the consequences.

The new rules made the county office a little slower, but accidents dropped a lot. The merchants later understood too: being able to speak is just a skill; being able to affix a seal is what changes the world. Any step that changes ledgers or rights must be separately seen, constrained, and recorded.

Reveal

This story is about: actions

An action is a discrete operation an Agent performs in the environment, usually through tools, functions, APIs, browsers, or GUI automation. It differs from an ordinary text response: an action changes the state of an external system, such as sending an email, modifying a record, creating an order, submitting a form, or calling a payment interface. Enterprise Agents must treat actions as authorizable, verifiable, idempotent, and auditable execution units, rather than equating model output directly with a completed business operation.

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

  • County office replies: the model generates suggestions, explanations or text responses
  • Stamp: the Action an Agent performs on the external world
  • Changing ledgers, posting notices, issuing tax receipts: tool/API calls that change system state
  • Think three more times: improving only model caution without action boundaries
  • Object, parameters, permissions, receipt: actions require clear input, authorization, and execution results
  • Tax receipts cannot be reopened repeatedly: idempotency and duplicate-execution risk
  • If no reply is received, you cannot stamp it again: action execution must distinguish between failure, timeout, and already effective
  • Dedicated box for the official seal: high-risk actions must be separately controlled and audited

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.

toolskillactuator
京ICP备2026014272号