After the human answers, does the job finish itself?
This is the follow-up nobody expects, which is why it works. The vendor has just told you the agent pauses for approval and you have nodded, because a pause is what you wanted. Ask what happens in the second after your yes lands. The answer decides whether you approved a message or sent one, and you will not find the difference in any demonstration, because in a demonstration the yes and the send are supposed to feel like one thing.
Two acts, or one
Approving a drafted reply and sending it are separate judgements. The first says the wording is acceptable. The second says it goes now, to that person, from that account, in a world that may have moved since the draft was written.
The reference design keeps them apart. When the person answers, the run records the decision and stops; a person restarts it, and it resumes from the state saved at the pause rather than from a fresh attempt at the task. The same rule governs the approval points inside a longer piece of work, both settings on the Register, the standing page of every setting in ArkOne’s reference design for an executive agent.
Two things follow. The record carries the yes and the act as separate entries, each with its own time and its own name against it, and because entries are added rather than edited, the order stands as evidence afterwards. And there is a moment between them in which somebody may notice that the client rang this morning.
One yes, counted two ways
Suppose the renewal invented for this work. You have read the drafted reply, it holds the list price and offers a volume tier, and you approve it between two meetings on a Tuesday morning. Both designs then do exactly what they were built to do.
| Counting after your yes | The run stops | The run continues |
|---|---|---|
| Entries left on the record | Two: the decision, then the act | One: the decision, with the act inside it |
| Moments the work can be stopped | One, before the restart | None |
| Who performs the send | The colleague who restarts it | The approval itself |
| What the client receives | The draft you read | The draft you read |
| If the client rang this morning | Somebody may notice | Nobody is looking |
Exhibit 1. Illustrative. One approved reply, counted by what each design leaves behind and where it can be stopped.
One row was made identical on purpose. Most of the time the two columns deliver the same message to the same client, which is precisely what keeps the difference invisible in a meeting. What separates them is the count of chances to change your mind, and one column has none.
Your auditor cares about the first row. One entry saying approved and sent cannot answer who sent it, because the answer is a rule. Two entries can, and the second carries a person’s name. That distinction costs nothing until the morning somebody asks how a particular offer reached a particular client, at which point it is the only thing that answers.
Where the second gesture shows up
A good answer describes the second act plainly. Your reply is recorded, the run stops, and somebody restarts it from the saved state. It will usually come with the reason: an approval is a judgement on a draft, and a draft is a thing that ages.
What you will hear instead describes the convenience. You approve in the chat and it carries on, or you tap approve and it handles the rest. Both are true descriptions of a good experience, and both answer that the two acts are one. Nothing in either sentence is dishonest; the vendor is describing the feature they built, and the feature is speed.
Two follow-ups separate the designs. The first is what is saved at the moment of the pause, because a run that resumes by thinking again may compose a different message from the one you approved, and your yes will have attached to a draft that no longer exists. The second is whether the record shows one entry or two, and whose name is on the second.
There is an honest case for continuing, and a vendor who makes it is worth more than one who denies the trade: a hundred small approvals a week are not improved by a hundred restarts. The question is which actions deserve the gap, and whether your company chooses the list. The question about a slow human is where that list is drawn.
component: answer-card
Asked plainly
Does an AI agent carry on by itself once a human approves?
That depends on a setting. One design records the decision, stops the run, and waits for a person to restart it, so approval and action are two separate acts with a gap between them. Another treats the approval as the signal to resume and finishes the work in the same motion. The second is faster and gives you no second look.
Why would a design deliberately stop after an approval instead of continuing?
Because it separates two things that a busy person conflates. Approving a drafted message means the draft is acceptable. Sending it means it goes now, to that person, from that account. Keeping them apart leaves one moment to notice that the client called this morning and the draft is already out of date, and it puts two entries on the record rather than one.
How do I check whether an AI agent resumes from what I actually saw?
Ask what is saved at the moment it pauses. If the state of the work is written down at the pause, what proceeds afterwards is the thing you read. If the run simply starts thinking again when your reply arrives, it may reason its way to a different message, and your approval will have applied to a draft that no longer exists.