First, what are we building?
Before describing how a control is assembled, we give it a family name. That is the first level.
The control type
A top-level key such as table, select, form, or card tells us the broad kind of control we are talking about.
It answers one simple question: What type of control is this?
Which kind of that control?
A control family can have more than one useful form. The second-level key gives that form its name.
table → simple
A table definition with a column group, header, and body instructions.
table → bodyOnly
A table variation whose instruction list builds the body only.
accordion → simple
The simple accordion variation.
accordion → flush
A different accordion variation, with its own base spec.
Why keep these levels separate?
Because “table” and “bodyOnly” answer different questions. The first tells us the family. The second tells us which member of that family we mean.
If we put every variation at the same level, the reader would have to infer which names are control types and which names are variations. The two levels make that relationship visible.