Produced by the profile's component mapping. Changes when the profile changes.
Shape · Learn · Guide
An override is a promise to maintain it
Component shape tokens inherit from the profile until you override one. After that the value is pinned: it survives a profile change, which is exactly what you want for a deliberate exception and exactly what you don't want for a value you set once and forgot. The difference between the two is visible here, not at publish time.
Computed from another token — a complete shape composed from corner values, for instance. Follows its source.
Set by you. Frozen until reset, and listed in Customize so it can never hide.
Before you override
- Is the whole family wrong? If controls everywhere feel too round, that is a profile or a scale value — one change instead of twelve.
- Is it one part, on purpose? A search field that should stay a pill while every other input squares off is a genuine exception. Override it and it will survive.
- Does it still differ? An override whose value equals the inherited one is noise: it will silently block the next profile change from reaching that part.