How a Signal Reaches a Member

How a Signal Reaches a Member A sequence diagram generated by Archify. unusual activity on a token screen the token verdict live feed + level alert, under 1s side panel updates, alert window opens signal message, median 17s notification on desktop and phone signal added to the record stats, charts and watchlists screen lands late, message edited in place Detect + screen Delivery Record + corrections The Market · live token activity · Sequence participant The Market live token activity The Engine · detection + conviction · Sequence participant The Engine detection + conviction Safety Check · per-signal screen · Sequence participant Safety Check per-signal screen Member's Panel · Chrome extension · Sequence participant Member's Panel Chrome extension Discord · signal channel · Sequence participant Discord signal channel Dashboard · stats + history · Sequence participant Dashboard stats + history Member · desktop and phone · Sequence participant Member desktop and phone Legend request return security async trace default message

Detection

  • • The engine watches token activity continuously, on every chain it covers
  • • A candidate is screened for safety before anything leaves the system
  • • Level and conviction are decided at the moment the signal fires

Delivery, measured

  • • Chrome extension panel: under one second from publication
  • • Discord: median 17s from firing, 8 in 10 under 30s
  • • Dashboard: the same signal, kept with its full history

When the screen is late

  • • A late safety result is never left hidden
  • • The message already sent to Discord is edited in place to carry the warning
  • • The record keeps what was sent and when it was sent