Skip to main content
See Iconography 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.

Gaps in the current rules

  • The Icon suffix is unexplained. 27 of 154 exports carry it, with no consistent rule for which one does. ErrorIcon is the plain glyph, and its ErrorOutline and ErrorRounded siblings carry no suffix; CheckCircleOutlineIcon is the outlined variant, and its plain CheckCircle and rounded CheckCircleRounded siblings carry none. The suffix does not mark a glyph style, avoid a name collision, or follow any other visible pattern.
  • Three variants of several glyphs ship with no selection ruleCheckCircle, CheckCircleOutlineIcon, and CheckCircleRounded; Info, InfoOutlined, and InfoRounded. Nothing says when filled, outlined, or rounded is correct, so the set is effectively three overlapping sets.
  • No process is documented for proposing a new icon, though TITAN-ICO-01 requires one.
  • icon-with-tooltip-max-width (300px) is a component token in the icon namespace. It belongs to IconWithTooltip, not to the foundation.
  • No icon-to-meaning registry exists. TITAN-ICO-07 requires one glyph per meaning, but there is no published mapping to check against.

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.
Last modified on September 2, 2026