Activity

[joebudi]

Goal

Provide a clear, reliable view of everything that has happened within an operation so users can understand, debug, and trust how work is executed. Activity is the system’s source of truth for history.

---

Problem

Today, users lack a clear way to understand:

• what the agent did
• what actions were taken
• why a request is in its current state
• what went wrong (if anything)

Without this:

• the system feels opaque
• debugging is difficult
• trust in automation is low

At the same time, mixing this level of detail into the main experience creates noise and confusion.

---

Solution

Introduce an Activity tab as a dedicated, chronological log of all request activity.

Activity should:

• show all requests across the operation
• display a timeline of events for each request
• include key events such as:
  • request created
  • agent evaluation
  • action proposed / executed
  • escalation triggered
  • retries / failures
  • completion

The focus is not on action, but on traceability and clarity. Activity is read-only and complements Overview (which shows current state).

---

User Flow

1. User opens an operation

2. User navigates to the Activity tab

3. User sees a chronological list of events across requests

4. User selects a specific request

5. User views a detailed timeline of everything that happened:

   • what the agent did
   • what actions were taken
   • how the state changed

6. If needed, user uses this information to:

   • understand behaviour
   • debug issues
   • verify outcomes

---

Summary

Activity provides a complete, transparent history of execution.

It answers:

“What exactly happened?”

While Overview answers:

“What is happening now?”