There is a misconception that grayscale is neutral. That it is the blank canvas, the zero state, the nothing-yet. Designers talk about “adding color later” as if grayscale is the before and color is the after.
This is wrong. Grayscale is a decision. A strong one.
In 1923, Laszlo Moholy-Nagy at the Bauhaus argued that the study of light must precede the study of color. You cannot understand what red does to a composition if you do not first understand what light does without it. Grayscale is not the absence of color. It is the study of light alone.
Every pixel on a grayscale screen is a lightness value in OKLCH with chroma set to zero. Zero chroma is not zero information. It is maximum clarity about one dimension: how bright is this? How much does it demand your attention? Where does your eye go first?
When a design system ships grayscale defaults, it is making three arguments at once:
First: hierarchy is more important than decoration. A page where you cannot tell the primary action from the secondary one does not need more blue. It needs better lightness contrast. Grayscale forces you to solve hierarchy before you solve aesthetics.
Second: every color you add should earn its place. On a grayscale page, a single blue link is a beacon. Two colors are a conversation. Five colors are an argument. Grayscale is the environment where you learn what each color costs before you spend it.
Third: the system works before the designer touches it. This is the hardest argument for designers to accept. A design system that requires configuration before it functions is a system that puts tooling before users. Grayscale ships a usable interface. Color makes it yours.
The rafters default is not “no color yet.” It is “light is enough.”