The channel box, five ways

Same three channels, same real fields, five treatments. Every number below exists on the payload today (today.messages.<channel>, errors24h, lastInboundAt, gates) unless a box says otherwise — a mockup is a promise, so nothing here is drawn that the API cannot produce without saying so.

A · Stat tiles

Key:value as the real stat-tile contract — label above, value below, a delta against a named period. Figures are proportional, not tabular: tabular gives every digit the width of a zero and makes a standalone number look loose. Gates keep their own row as status chips, word plus colour.

B · Spec sheet

Key:value at its most literal, and the version that actually earns the pattern: one label column, one value column, values right-aligned on a single spine, tabular figures because this genuinely is a column. Every field the payload carries, nothing invented, nothing interpreted. Scans like a datasheet.

C · Tiles with a trend

The stat tile's optional fourth part: a 14-point sparkline, body in the de-emphasis grey and the current step in the accent. Answers the question a bare count cannot — is today normal for this channel. No bars anywhere; a line is not a bar chart.

D · Descriptive, three rewordings

One treatment, three voices — same channel, same facts, so only the wording is under review.

E · Evidence instead of claim

The novel one. Every other treatment asserts the channel works. This one shows it: the last thing a person said and the last thing the bot sent back, with the gap between them. A working channel proves itself; a broken one is obvious because the last exchange is stale or one-sided. The status word stays, but it stops being the evidence.