AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
ENไทย中文
system-detail K.PUBLIC.SYSTEM

rgbm

RGBM

The semantic color role system of the AENET public UI. Components reference roles (navigation, action, insight, guard, system, warning) — never raw color names.

Status: active Last updated: 2026-08-16

System ID

rgbm

Status

active

Architecture layers

  • L2 Public Application (visual)

Inputs

  • Semantic role definitions (design/rgbm.json)

Outputs

  • Role tokens consumed by CSS and components

Public interfaces

  • design/rgbm.json
  • ui-contract/colors.json
  • web/assets/data/rgbm.tokens.json

Connected systems

Security boundary

Pure client-side design token system. No data, no network, no private systems.

Data direction

Roles → tokens → CSS/components. Client-only.

What

Give every public component a stable, semantic color vocabulary so color meaning survives theming and consistency is enforceable.

Why

Raw colors drift and become meaningless across components. RGBM replaces them with semantic roles that carry intent (navigation, action, insight, guard, system, warning).

How

Roles → tokens → CSS/components. Client-only.

  • Define semantic color roles (RGBM.NAVIGATION.BLUE, RGBM.ACTION.GREEN, RGBM.INSIGHT.MAGENTA, RGBM.GUARD.RED, RGBM.SYSTEM.CYAN, RGBM.WARNING.AMBER)
  • Keep design/rgbm.json the single source of truth
  • Prevent components from referencing raw color names

Example

A component that needs a "success" meaning uses the SUCCESS role token (design/rgbm.json, web/assets/data/rgbm.tokens.json) instead of a hard-coded color.

Inputs

  • Semantic role definitions (design/rgbm.json)

Outputs

  • Role tokens consumed by CSS and components

Dependencies

ui-contractaenet-cloud-public

Lifecycle

  • RGBM v1 (4 roles)
  • RGBM extended (6 roles: + system, warning)

Use cases

  • Components use role tokens for consistent meaning
  • Theming and accessibility rely on semantic roles

Limitations

  • Roles only — components must never hardcode raw colors
  • Visual system only, no data semantics

Connected systems

  • AENET Cloud Public — The public-facing entrance and observation layer for the AENET ecosystem. It publishes sanitized snapshots, static pages, a public API and an anonymous traffic channel — nothing more.
  • UI Contract — The single source of truth for the public UI structure — pages, navigation, components, coordinates, states, motion, colors, typography and locales — consumed by both the web and Swift renderers.
  • XGRID — The adaptive spatial grid system of the AENET public UI: desktop 12 / tablet 8 / mobile 1 columns, content-intrinsic sizing, with a 1920x1080 canvas used only as a design reference.

Questions people ask

These questions are answered by the content on this page.

  • What is RGBM?
  • What color roles does RGBM define?
  • Why does AENET use semantic color roles?

Evidence

Verified states only — nothing on this page is a prediction.

  • design/rgbm.json
  • ui-contract/colors.json
  • web/assets/data/rgbm.tokens.json

Next step