# Button variants

Button variant names have the same visual meaning across domains.

| Variant | Resting appearance |
| --- | --- |
| Primary | Blue fill |
| Secondary | Neutral fill: black in light mode, appropriately inverted in dark mode |
| Tertiary | Border with no fill |
| Ghost | No border or fill |

## Choose the treatment

A page's main action can use Secondary. For example, the public website's main call to action uses a black Secondary button. Importance is communicated through placement, grouping, and context; a page does not need a Primary button. Use at most one Primary button per decision region.

Do not redefine Primary as black for a website or change variant meanings through domain-specific overrides. Domain routing still selects broader design guidance; ask when the domain is unclear and retain established answers. An explicit user-selected style or theme can override aesthetic defaults.

Danger is a separate semantic treatment for destructive consequences, not a fifth hierarchy level. Preserve its warning meaning, accessible contrast, focus indicators, and disabled states. Ghost and Tertiary may acquire state backgrounds on interaction; their names describe the resting treatment.

## Implementation

Use the installed `@mirror-physics/fractal-ui` component and inspect its actual exports, props, tokens, and supported states. Text and icon-only buttons follow the same variant meanings. Preserve readable contrast in both themes, including at least 4.5:1 for normal-size enabled button text.

This draft defines the target policy. It does not claim that the current package implements all four variants. During production migration, update the owning component package and then migrate consumers, including changing public-website CTAs from Primary to Secondary. Do not simulate the new policy by globally recoloring Primary.
