events-manager

name	events-manager
description	Describes the NDB2 Events Manager (eventsManager) as the root typed game-event bus for user/game-engine actions. Use when adding a new game event, emitting events from routes/monitors, or wiring downstream consumers like v2 webhooks.

Events Manager (Game Events)

What it is

• app/src/domain/events/events-manager.ts exports eventsManager, a singleton typed event emitter for game events.
• A “game event” is something meaningful to players/observers (user actions or game-engine actions), not low-level internal signals.
• Other systems “fan out” from it (e.g. app/src/domain/webhooks/config.ts sends v2 webhooks for selected events).

When to use it

Use eventsManager when:

• A prediction state changes in a user-relevant way (triggered, judged, snoozed, etc.)
• A user action happens (new prediction, vote, bet, snooze vote, edits)
• A monitor/game-engine action happens that players should know about

Avoid eventsManager for:

• purely technical events (cache hits, cron heartbeat, retries, background job bookkeeping)
• internal invariants / orchestration signals that aren’t meaningful outside the service

How to add a new event (repo pattern)

1. Add the typed event name

   • Update NDBEvents in app/src/domain/events/events-manager.ts.
   • Payload types should usually be v2 DTOs (commonly API.Entities.Predictions.Prediction).

2. Emit it at the source of truth