Incident Response Chat Block for Solid

Everything. The team's replies come from a short typed script keyed on words such as "rollback" and "customer", the update form only changes local state, and paging adds a name to the list: nothing is published, paged or sent, and the line under the composer says so. To wire it for real, publish the card where postUpdate builds it, call your paging service where pageNext runs, and append your team's messages to the same list as they arrive.

It isn't stored anywhere: the pinned card is the newest update card in the thread, found by one pure function. Post a new update and it becomes the pinned one, the update count and severity in the top bar follow it (a major impact reads SEV 1, a partial one SEV 2), and the older cards stay in the thread as the record.

No. Impact is a word ("Partial impact" or "Major impact") with a glyph shape, a triangle or an octagon, and severity is a word in the top bar. Nothing relies on a color to be understood.

Enter sends and Shift and Enter add a line, which the field's description says for a screen reader; Enter during text composition (an IME) is left alone. Send stays quiet while the field is empty and says so if pressed, and focus stays in the field after sending.

The log is a focusable region announced as a log, so new messages are read out once, and every message starts with a hidden "Teague Marlow, 09:38". The form's fields have visible labels, the status line is one polite live region that reports what changed, and focus returns to "Post an update" after posting or cancelling.

The window keeps its height. A switch under the top bar shows the chat or the on-call pane, one at a time; the pinned update stays above the chat, the form stacks its two selects, and only the log and the pane scroll.