middleware-handlers

What problem does it solve?

The EventBus handles all asynchronous communication and lateral routing across the swarm. The rules here dictate how to govern this middleware logically without generating traffic mock buffers.

Core Features & Use Cases

• HMAC-SHA256 signing and verification: Every message on the bus must be signed by the agent's key and verified by the receiver; key rotations occur every 30 days to ensure credential freshness.
• No bypass rules: Do not allow unsigned inputs onto the bus unless strictly flagged for Tier 0 ingestion bypass processing.
• Reliability & isolation: When multiple subagents subscribe to a topic, an exception in one handler must not crash the publish queue; test this by injecting a bad event and confirming the good handler still executes.
• Resource controls: Cap in-memory event buffers (e.g., 5000) and spill unprocessed events to disk journaling; decorate slow consumers with timeouts.

Quick Start

Configure the EventBus to sign messages with the agent’s key and verify signatures on receipt.