Perishable reward events.
Delivered with context.
StreamAlert is the public event and future delivery layer for reward-graph changes. It is not an editorial newsroom, viewer-progress tracker, claim bot, or generic follower/subscriber/tip alert marketplace.
Public board
A human-readable projection of validated, perishable reward events with stable IDs and source links.
Personal delivery
Future consented watchlists and destination rules owned by ALERT-001—not working in this prototype.
One Discord bot
One network install funnel instead of separate bots for Drops, Badges, Emotes or Overlays.
Durable content elsewhere
Roundups, histories, guides and analysis stay outside StreamAlert; PROD-003 decides their home.
Truth and corrections
Every production event must bind its source, observation time, effective window, freshness, conflict state and correction lineage. Stale, retracted or unsupported facts fail closed. Campaign details link to StreamDrops; badge acquisition links to StreamBadges.
Contract limits today
Claim-window and badge-availability event kinds remain future work. The current alert preference model also cannot express the full destination-by-event matrix shown in these concepts. The prototype labels both gaps instead of presenting them as live behavior.
Privacy and platform boundaries
Does StreamAlert read viewer progress or claim rewards?
No. It models public reward rules and event timing only. It never auto-watches, auto-claims, or reports personal progress.
Are watchlists or delivery settings stored here?
No. Form controls update only the current page preview. There is no account, server-side save, push subscription, email capture, webhook storage, or Discord install.
Is StreamAlert affiliated with Twitch or Discord?
No. It is an independent fan-tool concept. Platform names identify sources or future delivery destinations, not endorsement or partnership.
How will corrections work?
A production correction must reference the previously delivered event, preserve its lineage, stop stale delivery, and expose the corrected source-backed state.