Real-time Events
Circuit + Pulsar: how events move between services.
Real-time events are how Runline's services stay in sync as work happens. They are carried by Circuit, the org nervous system, which is the only thing that touches the underlying message broker. A service never talks to the broker directly: it calls Circuit's HTTP API, and Circuit fans the event out to everyone who cares.
Why a single door to the broker
Putting one service in front of the broker keeps the event layer governable. Access, topic naming, and delivery are enforced in one place rather than reimplemented by every service. Topics are shaped by org, domain, and Runline, so an event is addressable and scoped, and one credit union's events never reach another's services.
How it is used
When a change lands (a new alert, a posted transaction, a completed Item), Circuit turns it into an event, and the Knowledge Fabric, the Runner fleet, and any interested service react in near real time. This is what keeps a Runner acting on what is true now rather than last night's batch.