Activity

Activity is the timeline that makes agent work explainable.

It combines task logs, session lifecycle events, structured AgentEvent records, and optional transcript references so humans can understand how the project arrived at its current state.

Open the Activity prototype

Why It Matters

Agent sessions are easy to interrupt and hard to audit if all context lives in chat.

Activity gives the project a durable trail:

• which agent claimed work;
• what decision blocked progress;
• how the user answered;
• which structured event continued the task;
• what evidence was recorded at completion.

This is especially important when a task does not simply succeed or fail. Many useful tasks pause because the agent needs a product, design, dependency, or scope decision.

Decision Flow

Sinaris treats a decision request as a first-class task state.

1. The agent reaches a genuine decision point.
2. It requests a user decision instead of failing the task.
3. The Hub shows the task as needing a decision.
4. The user replies from the task detail or Activity view.
5. Sinaris records a task.decision_resumed event and queues it for the owning agent session.
6. The agent resumes the same task without claiming new work.

The Activity view is where that handoff becomes visible.

Event Sources

Activity is intentionally not built from raw chat transcript inference.

Source	Purpose
Task logs	Claims, completions, failures, releases, and task evidence.
Session events	Registration, heartbeat, disconnect, context snapshots, and runtime lifecycle.
AgentEvent	Assignment, continuation, decision resume, queue auto-claim, resume context, and user message handoffs.
Transcript refs	Optional supporting context for reviewing the underlying host-agent conversation.

What You See In The Hub

Activity should answer:

• What just happened?
• Which agent did it?
• Which task or dispatch does it belong to?
• Is this event informational, blocking, or actionable?
• Can I reply to the agent or resume the task from here?

The mobile prototype highlights this because many interruptions are handled outside a full desktop review session.

Related Entry Points

Need	Entry point
Request a user decision	sinaris task decision-request
Resume after a decision	sinaris task decision-resume
Resume an agent session	sinaris agent resume
Inspect activity	sinaris hub