nx_genrole.nx

nx_genrole.nx -- THE single answer to "what is this file". One classifier, three consumers. This exists because the rule had already been written twice: nx_gen_modelid's main() and nx_gen_zoo's zo_classify() each carried their own copy of the tensor-name probes. The zoo's own header even claimed it "reuses nx_gen_modelid's probes rather than re-deriving them, because two copies of a classification rule drift and the drift is silent" -- and then re-derived them. ★★★★★ A COMMENT ASSERTING DRY IS NOT DRY. The second copy was already missing the adapter-family resolution (kohya vs peft prefixes) that modelid had learned, so a LoRA the front door named "z-image" the zoo named only "adapter-lora(kohya)". They had ALREADY drifted. ★ FILENAME AND EXTENSION ARE CLAIMS; THE TENSOR NAMES ARE EVIDENCE. Probing names is the only honest signature: a .safetensors DiT can be Z-Image or FLUX, a .gguf can be a DiT or an LLM, and a file sitting in the diffusion/ folder can be an adapter that is not a model at all. It REFUSES to guess. UNKNOWN is a verdict, never defaulted to the family we happen to support -- a wrong family runs to completion and produces a wrong picture with no error anywhere. license_tier: ORIGINAL