Frame badge and emote
presence with restraint.
A future aggregate could describe permitted public presence patterns for badges or emotes. “Adoption” here is shorthand for a precisely defined aggregate—not a claim about personal ownership, sentiment, value, or audience identity.
Illustrative analysis frames
values intentionally omittedBadge presence over governed periods
Values omittedEmote presence over governed periods
Values omittedWords that need definitions
before any number appears- Presence
- A qualifying observation on an explicitly approved public surface—not proof of ownership.
- Adoption
- A named aggregate with a disclosed numerator, denominator, period, and coverage statement.
- Unique
- Not publishable until the identity, deduplication, privacy, and threshold rules are approved.
- Trend
- Comparable governed periods with consistent collection and visible missingness—not a decorative slope.
Identity stays with the catalogs.
StreamBadges and StreamEmotes own collectible identity, meaning, provider attribution, acquisition guidance, and corrections. StreamStats would consume reviewed identifiers rather than rebuild those catalogs from observed labels.
Helix approval is necessary, not universal.
GOV-003 must establish the aggregate posture for Twitch Helix. Any supplementary badge, emote, or chat-derived source would still need its own terms, rights, privacy, retention, and publication review before it could contribute a result.
Aggregates wait for a governed data posture.
Real measurement requires GOV-003 to define permitted Twitch Helix aggregate collection, source attribution, observation windows, retention, corrections, freshness, and safe public thresholds. Until that posture is approved, StreamStats publishes no measured result.