Here is a list of all concepts with brief descriptions:

Nwelder
Nnaming
Rname_style	A name style names every kind of entity welder can bind, through one hook per kind
Rcaster_oracle	The one bindability fact a backend must provide: can it natively convert a type without welder registering it?
Rdoc_style	A style folds a welder::detail::function_doc into one docstring, and a welder::detail::enum_doc (an enum's summary plus its enumerator docs) into the enum's class docstring
Rresolution	The contract a resolution — the carriage's which-participates policy — must satisfy to be injected as welder::carriages::basic_carriage's Resolution argument
Rrod	The contract a rod (a welder backend, welder::rods::…::rod) must satisfy to plug into the generic driver
Rrod_binds_containers	Does rod B implement the optional bind_container hook (i.e
Rtwo_phase_rod	Does rod B opt into the driver's two-phase namespace sweep — register every welded type's NAME, bind the opaque containers that use them, then fill members?