cfn-event-bus

Pub/subscribe event routing enables decoupled communication across agents and system components. This event bus provides topic-based routing with structured JSON payloads, letting you publish lifecycle events and subscribe to agent state changes without direct agent-to-agent coupling.

Yes. The event bus logs agent spawn, completion, failure, and timeout events, plus gate and consensus signals. It maintains centralized lifecycle tracking so you can monitor agent state transitions and coordinate multi-agent tasks through event subscriptions.

The event bus supports optional Redis persistence for durability and cross-process coordination. You can enable Redis storage to persist events and enable agent synchronization across distributed CFN Loop workflows while maintaining in-memory performance when Redis is disabled.

The event bus applies JSON schema validation to structured event payloads and routes messages by topic. You configure filtering rules and validation schemas to ensure only valid events propagate and subscribers receive only relevant topics for their workflow stage.

Use the provided Node.js bridge to emit events directly from your application code. The bridge handles payload serialization and topic routing, letting you publish lifecycle and gate events into the centralized bus without managing transport or formatting manually.

Yes. The event bus supports trace propagation to track event flow across agents and system components. Combined with debug configuration, you can log event paths, monitor statistics, and correlate events across your entire CFN Loop workflow for troubleshooting.