Activity Timeline

The audit trail of alignment — who voted, who flipped, what status changed, and on which version of the brief.

Overview

The Activity tab is a version-grouped, append-only log of what's happened on a brief. Alignment votes, Brief status transitions, and document edits all appear here, bucketed by the version of the Brief they happened against. If someone raised a concern on Version 3 and it was resolved by Version 4, the whole progression is visible in one scroll.

The timeline is the visible artefact of the Align leg of the loop. Refine produces the Brief, Align is the team converging on it, and the timeline is how everyone sees that convergence happening.

Activity timeline showing team alignment grouped by document version

The Activity tab updates in real time. New votes, status changes, and comments appear as soon as they're submitted — no refresh needed.

How It Works

Open the Activity tab — Inside any Brief, click Activity in the document panel.
Scan the team overview — The current version is expanded at the top. A circular progress indicator summarises alignment — green when everyone is aligned, yellow when there are outstanding concerns.
Browse by version — Activity is grouped under collapsible version headers (Version 1, Version 2, …). Each group shows the votes, status changes, and edits that happened while that version was current. Older versions stay collapsed by default; click to expand.
Cast or update an alignment vote — From the Brief, mark yourself Aligned or flag a Concern. Each vote is appended to the timeline as a new entry, so flips show up in the version they happened on. Cleared votes are recorded too, but excluded from the alignment count.
Read concerns — The "Concerns" section lists members who flagged issues, along with their comments explaining what needs resolution.
Act on feedback — Use the comments to update the Brief or continue the conversation in the chat panel. When a concern is resolved, the member can update their vote.
Load older versions — Use the "Load more" button at the bottom of the timeline to page through earlier versions.

Key Capabilities

Version-grouped timeline: Activity is bucketed by document version, not just chronologically. You can see which feedback was given against which state of the brief.
Append-only votes: Every vote — including changes and clears — appends a new entry. The timeline never rewrites history, and realtime delivers new entries instantly.
Status changes are first-class: Brief transitions (Draft → Refining → Aligned → Shipping → Done) appear in the timeline alongside votes. Status changes triggered by the AI agent show up here too, attributed to Hamster.
Live updates: New votes and status changes appear immediately without refreshing the page. The tab also recovers cleanly when you return to it after a break.
Member identification: Each item shows the team member's name and avatar; AI-driven changes show the Hamster avatar.
Pagination: Load older version groups on demand. A failed load leaves the existing timeline intact and surfaces the error inline.
Context-aware empty state: New Brief with no content gets a different empty state from a Brief with content but no activity.

What Counts as Activity

The Activity tab tracks:

Alignment votes — "ready to proceed," "not yet," or a cleared vote.
Comments on votes — notes left alongside an alignment vote explaining the reasoning.
Status changes — transitions between Draft, Refining, Aligned, Shipping, Delivered, Done, and Archived. Status changes made by the AI agent through chat are logged here too.
Document version markers — references to the Brief version each batch of activity happened on. The actual content diffs live in Document Versioning.

Using Alignment to Move Forward

The Activity tab is most useful as a forcing function before generating a plan. Share the Brief, ask teammates to review, and check the timeline to see whether there's consensus.

Version grouping helps when concerns predate edits: if a stakeholder raised a concern on an earlier version and the Brief has since been updated, you can see whether their concern was addressed by the changes in a later version — and whether they've updated their vote to reflect that.

Tips

Share the Brief with stakeholders before generating a Plan and ask them to cast alignment votes. A Brief with documented alignment is easier to hand off and less likely to Result in rework.
Use the version grouping to trace decisions. If you need to know why a requirement changed, the activity history shows the feedback that prompted each revision.
Review the Activity tab during standups to see who still needs to weigh in.
If a teammate's concern has been addressed by edits, ask them to update their vote so the team overview reflects the current state.