Custom Event Bus Signals & Telemetry Triggers
Decoupled event-driven messaging, naming conventions for domain events, payload schemas, and telemetry instrumentation.
Published: 7/10/2026
The Aircada Event Bus provides decoupled publish-subscribe messaging across UI components, scene operators, and background analytics services.
Rather than tightly coupling operators to each other, systems emit standardized event signals (e.g., FINISHCHANGED, DIMENSIONRESIZED, ENGRAVINGUPDATED, CARTPAYLOAD_READY) carrying lightweight data payloads.
The Event Catalog in the Dev-Planner defines all project event channels, trigger types (USERINPUT, SYSTEMCALCULATION, LIFECYCLE), payload properties, and listening @System managers.
- UPPER_SNAKE_CASE Naming: Standard event signal naming (e.g. SWATCHSELECTED, PRICERECALCULATED, STEP_CHANGED).
- Payload Contracts: Explicitly document payload fields (e.g., { previousFinish: string, newFinish: string, priceDelta: number }).
- Telemetry Instrumentation: Events automatically log structured markers to .aircada/logging/dev-logs/ for automated testing assertions.
- Zero Hard Coupling: Systems subscribe via useAirEvent(eventName, callback) or @OnEvent(eventName) without direct class references.