Story Events and overlays

Emit meaning, not editing instructions

A Story Event describes a verified semantic fact:

• personal_best
• rank_gained
• target_cleared
• checkout_completed
• lead_changed
• match_won
• streak_extended

The bounded fact payload carries enough domain context for downstream consumers to explain the moment. It should not contain HTML, a file path, an OBS scene, provider credentials, or a request to publish content.

Story effects are processed only after the activity transition commits.

Retractions

If an authorized correction invalidates a committed moment, deterministic replay produces the corrected event set and the host emits explicit retractions. Editors and overlays can reconcile without pretending the first event never existed.

Read-only overlay

An overlay is a package artifact rendered from a bounded host snapshot. It may show activity identity, goal, current/final result, progress, pace or meaningful change, connection state, stakes, and the next milestone.

It cannot:

• send activity commands;
• control OBS;
• query member history;
• fetch arbitrary network resources;
• retain credentials;
• become a second scoring implementation.

Shared presentation primitives

The public Presentation Kit provides pure semantic framing, theme tokens, safe-area layout, formatting, reduced-motion behavior, and accessibility primitives. The package still decides what the viewer should care about and maps domain state into that model.

This lets Split Timer and Reaction Foundations share quality without looking or behaving like the same activity.

State matrix

Preview at least:

Test compact broadcast dimensions and full 16:9 layouts in addition to member phone, tablet, and desktop viewports.