Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
Published DS package ยท System Layer ยท Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Border radius is one of the fastest ways to feel an engine change.
Even when layout, components, and copy stay the same, corner treatment changes the emotional posture of the UI. Classic feels formal, Modern feels confident, and Rustic stays restrained.
Current md10pxDefault card and panel corner.
Current full9999pxChips, avatars, toggles, and pills.
Token count6 levelsEnough range without ambiguity.
Radius stack
`md` is usually the center of gravity.
none0
Hard edges for sharp containers and utilitarian framing.
tokens.borderRadius.none
sm6px
Minor rounding for inputs, pills, and low-emphasis controls.
tokens.borderRadius.sm
md10px
Default radius for cards, panels, and common containers.
tokens.borderRadius.md
lg14px
Visible softness for elevated surfaces and focused modules.
tokens.borderRadius.lg
xl18px
Hero-level framing for editorial or premium sections.
tokens.borderRadius.xl
full9999px
Circular and pill treatments for avatars, chips, and toggles.
tokens.borderRadius.full
Same scene, three engine personalities
Engine comparison
Radius heuristics
Use `sm` on controlsInputs, segmented filters, and compact utility buttons.
Use `md` for default surfacesCards, panels, popovers, and data modules.
Reserve `xl` for framingHero bands, spotlight sections, and narrative cards.
Use `full` semanticallyPills, avatars, badges, toggles, and circular affordances.
Radius usagePaste-ready example that shows the base contract first.