Taxonomy nodes

[akijakya]

The fact that nodes in the class taxonomies are valid classes has some interesting consequences, for example core/llm is a valid module with a free-form JSON as data field, clearly not intended to be actually used in records. Lets have a discussion about this problem!

[akijakya]

Solution could be as simple as removing nodes from the list of valid picks in the validators.

[akijakya]

Another solution could be to treat lower level nodes as subcategories instead of classes.

[akijakya]

Enum objects already work in a way, that they are not valid picks for the attribute they represent, only their children objects. We can transfer this logic to classes, removing the categories json files that only list the top level categories anyways, and treat node classes the same way as enum objects.

[akijakya]

Module classes are different from skills and domains in that these classes are actually being instantiated with real data. While it makes sense to use skill and domain nodes as part of the taxonomy, in the case of modules, they behave more like subcategories, not to be used as actual modules in a record.

So we could choose a hybrid approach: keep categories.json files, but add the feature for subcategories in them. Classes can belong to subcategories instead of extending another class for better organization, without the side effect for these subcategories to be treated as actual classes.