Type Alias KnobDescriptor<T>

Remarks

The point of describing knobs as data is that a caller — increasingly a coding agent rather than a person reading docs — can ask what a module actually exposes instead of guessing layer ids from training data. Three things follow from having it:

• ground before generating — write against what the module exposes, not what you remember;
• validate — ranges and allowed values arrive as data, so a bad value is caught before it is rendered;
• report and diff — the paired settings object is plain and serializable, so a display change is reviewable in a pull request.

A visual editor cannot do any of those: it cannot be read, diffed, or put in a pull request.

Modules narrow this shape with their own descriptor type — e.g. StylingKnobDescriptor requires available and appliesTo, while a module whose knobs are always applicable omits them.