Color

See Color for the decided part of this page.

Known issues

Divergences are where code and design intent disagree; open decisions are where nothing has been decided yet. Neither is resolvable by inference.

ID	Kind	What
TITAN-DIV-01	Divergence	Tier-3 tokens alias primitives, never semantics
TITAN-DIV-02	Divergence	`border-focus` is specified and never implemented
TITAN-DIV-03	Divergence	status colours fail contrast
TITAN-DIV-07	Divergence	no surface layering model
TITAN-DIV-09	Divergence	the naming specification and shipped tokens have diverged
TITAN-GAP-03	Open decision	the vocabulary was specified but never surfaced
TITAN-GAP-04	Open decision	seven groups of tokens share one value with no visible distinction
TITAN-GAP-05	Open decision	no selection rule where two tokens both apply
TITAN-GAP-13	Open decision	surfaces have no layering order

Gaps in the current rules

overlay-default is malformed — rgba(21, / 36, / 62, / 0.3000) is not valid CSS and browsers will drop the declaration. The dark value is well-formed.
background-neutral and background-disabled are identical (#e7e9eb). Two names, one value, different meanings — and one of seven such collisions. See TITAN-GAP-04.
link-default and link-visited are identical (#1c53e9), so visited links cannot be identified. See TITAN-GAP-04.
border-width-md and border-width-emphasis are both 2px, so their recorded distinction is invisible on screen. See TITAN-GAP-04.
No semantic focus token exists. See TITAN-DIV-02.
The light-mode status contrast failures are untriaged. Whether they are known and accepted or unnoticed is not recorded. See TITAN-DIV-03.
Surfaces have no defined layering order. Titan ships four background tokens that function as surfaces, with no defined order and no rule pairing a border to the surface it sits on. The ordering on the main page is a proposal, not yet signed off. See TITAN-DIV-07.

Constraints Titan should enforce

These are real, currently-true rules. Nothing in code stops a builder from violating them today — each is a placeholder for a guardrail Titan hasn’t built, not a decision still being made.

ID	Constraint	Would be enforced by
TITAN-COLOR-01	Component code references a token, never a hex value, `rgb()`, or a `*Channel` value.	A stylelint literal-value ban plus a `*Channel`-reference ban in `components/core` and consumer styles.
TITAN-COLOR-02	Text meets AA contrast against the surface it sits on.	The same build-time contrast gate as TITAN-A11Y-01.
TITAN-COLOR-05	Status color comes from the four defined statuses only.	The same literal-value-ban lint as TITAN-COLOR-01, applied to any color used in a status-labeled prop/slot.
TITAN-COLOR-06	Opacity is never used to derive a color variant.	A lint rule banning direct `*Channel` reference (same as TITAN-A11Y-08).
TITAN-COLOR-07	Status text/icons use `-alt`; bold fills never pair with `text-invert` for success or warning.	A lint rule hardcoding the two forbidden pairings as banned combinations, and requiring the `-alt` suffix for any status token used as `color`/`fill`.
TITAN-COLOR-08	Contrast is verified against `background-view-background`, not only `background-default`.	The same build-time contrast gate as TITAN-A11Y-01.
TITAN-COLOR-09	Hover color is never the sole interactive signal.	A lint rule scanning a component’s hover-state style block for changes that touch only color properties.

Registries

Foundations

Components

Patterns

Views

Content

Contribute

Known issues

Gaps in the current rules

Constraints Titan should enforce

​Known issues

​Gaps in the current rules

​Constraints Titan should enforce

Known issues

Gaps in the current rules

Constraints Titan should enforce