Concepts/Concept

ADPS Engineering Concept Registry

Execution vs Content Agents

Choose runtime controls from the deliverable, state dependency, and cost of failure.

Design differences between execution and content agents

Application context

The same model can draft a payroll-policy note and create a payroll group. The first task delivers text that a user can revise or regenerate. The second changes employee, payroll, and approval records; one misbound identifier can affect later steps and external systems.

Definition

Classify an agent by the object it delivers and the consequence of failure.

ClassPrimary deliverableState between stepsTypical controls
Content agentReport, answer, slide, draftMostly text and cited materialReview, citation checks, regeneration
Execution agentCompleted business changeIdentifiers, statuses, versions, approvals, receiptsState machine, idempotency, authority, rollback, external acceptance

Engineering mechanism

In expense processing, invoice upload must receive the application_id returned by the preceding create call. The runtime stores that value with tenant, source call, tool version, and timestamp, then injects it into the next request. The model can select the business route and explain the result; it does not regenerate the identifier from conversation text.

Boundary

Many systems contain both classes. Research may produce a draft before an approved action changes a record. Apply stronger execution controls at the point where state, money, authority, production configuration, or user rights can change.

Proposal and provenance

Initial source within ADPS
Initial practice: Bo Liang
First recorded in
Dongfang Yiteng execution-agent case ()
ADPS editorial work
ADPS turned delivery object, state dependency, and failure consequence into an architecture-selection test.
Current standing
Candidate concept

Initial source: Dongfang Yiteng Execution Agent case report; contributed by Bo Liang.

Concept registry · CC BY 4.0

Chronicle

Recorded source
Dongfang Yiteng execution-agent case ()
Source date
First published on ADPS

View in the ADPS Chronicle