Follow a game, publisher, badge, or claimed channel. StreamAlert turns source-backed reward changes into timely notices—without becoming another follower, tip, or subscriber alert-box marketplace.
Dead by Daylight: Jason had three rewards and a published campaign deadline.
Three rewards were present in the captured campaign. This example shows how a public graph event would link to requirements, eligible-channel scope, deadline, claim guidance, source and freshness.
The displayed lead time is a rule preview, not a current deadline. A production event only emits when its source-backed timestamp is fresh and unconflicted.
This event family remains future until the graph has a cited badge window and a validated change event. It links to the acquisition authority instead of duplicating it.
A followed game or publisher gains a source-backed reward campaign.
A known campaign or reward earning window enters the lead time you chose.
A published claim deadline is approaching. The notice links to official inventory; it never says you personally claimed.
A followed badge gets a cited acquisition window or a known availability change.
A claimed creator channel becomes eligible for a reward campaign tied to its category.
A game follow can cover new campaigns and deadlines. A publisher follow spans its games. A badge follow stays tied to its acquisition facts. A claimed channel can watch category-linked availability.
Short, source-linked notices after explicit browser permission.
One future install projects selected reward events into a chosen server channel.
Batch discoveries and upcoming deadlines instead of sending one message per change.
Signed, deduplicated graph events for a creator's own automation.
StreamAlert owns one install flow, token boundary, permission model, command namespace and delivery ledger. StreamDrops, StreamBadges, StreamEmotes and StreamOverlays link here instead of building separate bots.
“Drop live” and “ends in six hours” are StreamAlert events. Durable roundups, histories, guides and platform analysis stay outside this product while PROD-003 decides their eventual home.
The same item must not plausibly fit both perishable delivery and durable editorial. The public board and every delivery concept project one graph event; they do not become a parallel newsroom.
Real delivery requires deduplicated graph events, freshness and retraction handling, consent, endpoint verification, secret references, retries, opt-out, and delivery receipts. This static site demonstrates the product boundary while ALERT-001 remains gated.