Messages

Consecutive turns from one sender collapse into a run: one name, one squared tail corner on the last bubble. A day divider replaces per-message relative time.

System events sit quietly between messages without pretending to be messages. Exact-timestamp activities share one event and time, while each linked record keeps its own leading domain icon.

Success states are glyphs (a hollow clock, one tick, two ticks, two accent ticks) because they are glanced at, not read. Failure is the one state that takes words, next to the bubble that failed, because it is the only one needing action.

A name the sender chose for themselves and we could not match to any record. Rendered as a quotation after the address we do trust, never in place of it. Presenting an unverified name as fact is how a stranger gets to look like a colleague.

A calendar day, and the first unread message. Both resolve client-side, so a day divider can't say Today the morning after.

Same component, same geometry. Joey is identified by name without an avatar or animated glyph; the corner carries the time alone, since an assistant answer has no delivery state.

Every turn on the left, for a log where direction carries no meaning.

The template editor lives at the latest edge of the conversation, where the next reply would normally appear.

Messages can carry compact links to the record or task they refer to. The action row stays inside the bubble and below the message body.