Model catalog

The catalog is the source of models for tasks. The consensus part of an entry changes only through review in git; the storefront (badge, order, tags) — via the admin panel without a rebuild.

A registry entry

An entry carries the weights with their hashes (model_hash — what the network executes and verifies), the canonical execution spec, hardware requirements, the license, and a trust tier: Trusted — verified by the platform, Community/Custom — added by users.

Filters

Hardware class (consumer or datacenter — by required VRAM), model family, parameter size, quantization kind. GGUF in the quantization filter is an additional value on top of precision: a Q4_K_M entry is found under both Int4 and GGUF.

Storefront

The Featured badge, the ordering weight and the tags are assigned by platform administration and apply without a rebuild. The storefront does not affect execution, parameters or verification — those fields come from the registry alone.

Hardware

A model card shows the minimum VRAM and, where set, the recommended one. If the minimum is below the size of the weights themselves, that is a deliberate entry with partial component offload, not a mistake: slower, but working.