Alerts that say what happened and what to do, with the day named

What changed for people using Bellwether

• Alerts say what happened and what to do, in a sentence. Every alert on the Overview and in Activity is a short title that names what happened, one plain line that says what to do or what happens next, and a fold for the specifics. The long unformatted paragraphs and the internal names that had leaked into them are gone.
• A refused protective stop that later lands says so. When the broker refuses a protective stop because another sell order holds the shares and the retry a minute later is accepted, the row leads with "protective stop is back in place" and a "Restored 15:05" pill. The original refusal is kept behind "What happened at 14:30".
• The desk's own reports go to the right reader. When the desk notices two of the platform's readings disagree, or one of its tools failed, the report goes to the platform team, not your Overview. What stays is what you can act on: "The PM cannot follow the mandate as set" for the names involved, linked to Guidance.
• A missed check names the check, the cause and the day. "The 10:30 intraday check did not run" says why in one sentence and ends "The next check is at 12:30 CT; nothing for you to do." A slot left over from a previous day is closed out quietly, and lateness is never a negative number.
• A broker connectivity blip is not an incident. One failed pass of the trading service on a momentary broker or network error is logged as a warning; only five in a row, or a full minute without a good pass, is raised as critical. The service already retried and recovered in every such case.

What you may notice

• Alerts from earlier days carry the day: "Tue 14:30 CT" for the past week, "Sep 9" for older ones; today's rows keep the bare time.
• Tickers in an alert's title and line wear the same chip they wear everywhere else, and a repeated alert says "twice" or "3 times".
• The line you are meant to read is set in the brighter secondary text rather than the muted one, and nothing on a resolved row is struck through.
• A position that differs from the broker's records reads as one sentence ("0 on the books but 1.26 at the broker, and no order of ours explains it"), with the questions worth asking behind Details.
• When the broker refuses to move a stop, the row says where the stop stays and, behind Details, where it was being moved to; while the move is retried a small "Retrying every 60 s" pill sits next to it.
• When the platform changes how it reads a finished bar, the desk is told for a day and a half that an earlier reading may have shown a different number and that this is a restatement, not a data problem.
• The four alert rows from September 15 that prompted this work are re-worded and re-routed when read; nothing in the stored history was rewritten.

Known gaps and what’s next

• Activity keeps the bare time in its leading column because its rows sit under day headings; its expanded view adopts the Overview's folded note in a later release.
• More "problem" and "back to normal" pairs (the trading service stalling and recovering, live prices dropping and returning) will fold the same way once each pair is linked.
• A single missed check stays informational even when the one before it was also missed; the platform team is paged on repeats separately.