Monitoring

Attention queue across accounts

What still needs a person, worked out from what is currently true rather than from a feed of what happened.

Derived from stateThree severitiesTen signal kinds

The attention queue is the list of things still waiting on a human. It is deliberately not built from the notification feed, and that distinction is the most important thing about it. Notifications are an event stream with per-user read state: they answer what happened. This answers what is still true and still unresolved.

Those two diverge the moment somebody clears a badge. If the queue were derived from notifications, marking one read would delete the work item, and a winner would quietly never ship.

Every item is ranked into one of three severities: broken, needs a decision, and queue. The order is load-bearing rather than cosmetic, because a trust failure suppresses the result underneath it instead of sitting beside it. An experiment with a broken split may also be reporting a significant winner, and showing both would invite somebody to act on a number that cannot be read.

Items are stored as structured data rather than as rendered sentences, so the same signal can become a card today and something else later without a link frozen at query time breaking when a route changes.

Better experiments, better conversions

Test on all visitors with the world’s lightest script and make confident decisions powered by real-time reporting.