@tbbn/event-contracts
v0.1.0
Published
Typed event names/payloads shared by publishers and subscribers on the TBBN event bus. See docs/architecture/event-webhook-catalog.md.
Readme
@tbbn/event-contracts
Status: WORKING. Every event across every WORKING service is a fully typed interface in
src/events.ts (31 total — merchant/seller/API-key lifecycle, listing, offer, trade session,
reservation, checkout, fulfillment, moderation, fraud, notification), not a name-only placeholder
constant. See docs/architecture/event-webhook-catalog.md for the full catalog, publisher/
consumer table, and naming convention (noun.past_tense_verb).
Do not publish or subscribe to an event by a raw string literal anywhere in the codebase — always import the typed interface/const from here, so a typo or shape mismatch is a compile error, not a silent no-op subscription.
Publishing pattern used throughout the codebase: any service that needs to react to something
publishes directly via EventPublisher (Redis pub/sub); any service that needs to react runs its
own self-subscribing Redis subscriber. services/event-service is a passive dev-transport logger,
not a required intermediary — nothing is routed through it.
