Bus UI module baseline
Design Layers
The bus-ui module starts as a set of small reusable libraries built on the
implemented GX foundation through v0.1.15.
The first libraries cover common functional parts before assistant, terminal,
evidence, portal-host, or product-module concepts.
bus-ui is not one monolithic UI library. It can contain independent common
component libraries, runtime helper libraries, assistant UI, terminal UI,
evidence UI, and host integration libraries when those layers become concrete.
The dependency order is GX foundation first, then common bus-ui components,
then generic runtime helpers, then application-specific UI libraries. Each
library should depend only on earlier layers and keep provider authority,
product-specific workflow policy, and portal hosting in their owning modules.
- Product character defines the operational tone that higher product surfaces may apply.
- Content style defines app copy and error wording.
- Accessibility and safety defines accessible names, safe links, and raw-content boundaries.
- Common component patches then add icons, buttons, links, menus, tabs, panels, cards, layout helpers, shells, forms, inputs, tables, lists, timelines, and status surfaces.