Concepts/Concept
ADPS Engineering Concept Registry
Activity Events and Timeline
Record model, tool, state, latency, cost, and external results on one execution timeline.
Application context
A user reports that an agent selected the wrong template and stopped at approval. A platform trace shows model latency and tool spans, while the business reviewer needs the interpreted intent, route decision, parameter source, approval state, and external result on one timeline.
Definition
Activity Events provide a semantic execution record for one task. An Activity identifies a meaningful stage such as intent classification, planning, tool execution, approval, or verification. Frames within the Activity record model calls, tool calls, state transitions, duration, cost, evidence references, and visible output.
Engineering mechanism
Events share run_id, activity_id, causation, principal, component version, and redaction policy. The UI can show a business timeline while engineers open detailed frames under role-based access. Checkpoints and external receipts link to the same event chain, allowing replay and failure attribution.
Boundary
Provider traces remain useful for model and tool diagnostics. Activity Events add domain meaning and state transitions; they do not require prompts or private reasoning to be visible to every operator. Retention and detail follow risk, privacy, and audit policy.
Proposal and provenance
- Concept group
- Evaluation, reflection, and governance
- Initial source within ADPS
- Initial practice: Bo Liang
- First recorded in
- Dongfang Yiteng execution-agent case ()
- ADPS editorial work
- ADPS organized model, tool, state, latency, and cost events on one timeline.
- Current standing
- Case-derived name
Initial source: Dongfang Yiteng Execution Agent case report; contributed by Bo Liang.
Chronicle
- Recorded source
- Dongfang Yiteng execution-agent case ()
- Source date
- First published on ADPS