Reference
Reference
System state
Service locations and the path from an event to a reply.
On this page
Service map
The repository separates platform I/O, bot decisions, data ownership and web interfaces. Services communicate through NATS; the stream definitions and their retention limits are in pkg/bus/streams.go.
| Area | Code | Responsibility |
|---|---|---|
| Twitch ingress | app/twitch/ingress/ |
Receive and normalize Twitch events |
| Sesame | app/twitch/sesame/ |
Evaluate modules, commands and other bot behaviour |
| Twitch outgress | app/twitch/outgress/ |
Carry out Twitch actions |
| Data services | app/db/ |
Own application records and expose operations |
| Projector | app/projector/, internal/projection/ |
Maintain and serve derived state |
| External APIs | app/gossip/ |
Provider integrations |
| Web | web/dashboard/, web/admin/, web/marketing/, web/docs/ |
Dashboard, administration, marketing and documentation |
Common event flow
sequenceDiagram
participant T as Twitch
participant I as Ingress
participant N as NATS
participant S as Sesame
participant V as Projection
participant O as Outgress
T->>I: EventSub event
I->>N: Publish normalized event
N->>S: Deliver event
S->>V: Read channel state
S->>N: Publish action
N->>O: Deliver action
O->>T: Call Twitch API
This shows a common chat path, not every event or fallback. Ingress uses premium and standard lanes; Sesame carries priority into outgress. The implementation and configuration define the actual timeouts, retry policies and retention for each lane. A durable consumer is not a guarantee of infinite retention or exactly-once processing.
For state ownership and hydration see data and state. RPC types live under internal/domain/rpc/; RPC contracts provides a starting map. CONTEXT-MAP.md describes service boundaries and placeholders. Deployment manifests live under deploy/ and can change independently of these code boundaries.