See Radius 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 specification’s corner vocabulary doesn’t map to the shipped tokens. It names
corner kinds —
corner, hard-corner, soft-corner, round — which do not correspond
to radius-sm, radius-base, radius-md, radius-pill, radius-circle. Two vocabularies
for one concept, and neither is mapped to the other — already recorded above.
radius-base (3px) vs radius-md (4px) has no selection rule. A 1px difference is
at the edge of perceptibility, and nothing documents which surfaces get which. The
mapping on the main page is a proposal.- Why 3px is not recorded. The choice is deliberate; the reasoning is not written down.
- No nesting guidance exists upstream. The main page’s own constraint on this is a
proposal, not a confirmed decision.
- No
radius-lg. Whether large decorative surfaces are meant to use radius-md or
something larger is undecided.
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 17, 2026
