Source trail

Storybook

Where the answer came from

An agent that researches should show its working. The source trail lists what it opened, in order, each row a source chip with a status and a note on what the source contributed. A long trail collapses to one line, so the receipts are there without crowding the answer.

Default

  1. Design tokens quarterlyThe three-tier token architectureRead
  2. Colour contrast working group notesAA pairings for the action colourRead
  3. Component API changelogWhen the convenience callbacks landedRead

Streaming

Mid-research, the header counts and spins, the active row carries its own spinner, and sources the agent has queued but not opened sit quiet. Appended rows ease in; the motion is pure CSS, so reduced motion stills it.

  1. Design tokens quarterlyRead
  2. Colour contrast working group notesReading now
  3. Component API changelogNot opened yet

In a research answer

The trail pairs with reasoning: the thinking collapses above, the sources settle below, and both fold away once read.

The token architecture pages agree on the three-tier rule; the changelog dates the convenience callbacks to the same release that documented them.
  1. Design tokens quarterlyRead
  2. Colour contrast working group notesRead
  3. Component API changelogRead
  4. Release notes archiveRead

Linking out

A row with an href renders its chip as a link and opens in a new tab, so checking a source never abandons the conversation.

  1. Design tokens quarterlyRead
  2. Colour contrast working group notesRead