How a signal reaches a member

How a signal reaches a member A data-flow diagram generated by Archify. 01 / Market 02 / Engine 03 / Pyramid 04 / Delivery and record 05 / Member Solana + Hood soon · new tokens + trades · 01 / Market Solana + Hood soon new tokens + trades Signal engine · independent reads · 02 / Engine Signal engine independent reads Safety check · scams cut first · 02 / Engine Safety check scams cut first Level gate · climbs, never repeats · 03 / Pyramid · max 4 per token Level gate climbs, never repeats max 4 per token Chrome extension · Runner Printer inside · 04 / Delivery and record Chrome extension Runner Printer inside Discord · a channel per level · 04 / Delivery and record Discord a channel per level Global Stats · every call, kept · 04 / Delivery and record Global Stats every call, kept Member · desktop and phone · 05 / Member Member desktop and phone RunShots · Telegram + Discord · 05 / Member RunShots Telegram + Discord live activity candidate call cleared call pushed at once seconds later stamped when it fires card, alert, sound level role ping runs 4x or more Legend primary data policy / PII async batch data store data flow

Up only

  • • A token is called again only when it climbs a level
  • • The same level never repeats

Two seats

  • • The extension gets the card first, over an open connection
  • • Discord follows seconds later, one channel per level

The record

  • • Every call enters Global Stats when it fires
  • • Calls that run 4x or more become RunShots