Lower layers (data, scene, input) sometimes need to push state or
commands to specific UI panels — performance-monitor wants FPS
samples from the animation loop, data-loading-monitor wants
progress updates from the data manager, dimension-sliders wants a
"toggle me" trigger from the input handler. Direct imports would
violate the layer order documented in CONVENTIONS.md §10.
This bus is the dependency-inversion target. The event map below
declares every cross-layer event; publishers emit(...) and
subscribers on(...) against it with full payload typing.
Compared to the notifier (utils/cross-layer/notifier.ts) which has a
single backend and a fixed method dictionary:
the bus has open subscriber sets — many panels can react to
the same event;
panels can be constructed late without bootstrap-order
coupling — events with no listener are dropped silently;
per-event payload typing fails mistyped event names at the
call site.
Typed pub/sub bus for cross-layer events.
Lower layers (data, scene, input) sometimes need to push state or commands to specific UI panels — performance-monitor wants FPS samples from the animation loop, data-loading-monitor wants progress updates from the data manager, dimension-sliders wants a "toggle me" trigger from the input handler. Direct imports would violate the layer order documented in CONVENTIONS.md §10.
This bus is the dependency-inversion target. The event map below declares every cross-layer event; publishers
emit(...)and subscriberson(...)against it with full payload typing.Compared to the
notifier(utils/cross-layer/notifier.ts) which has a single backend and a fixed method dictionary: