Evaluator method registry must be backed by distinct execution paths

A method registry is insufficient when methods advertised as code, judge, or hybrid all dispatch to one execution path. Require each method to map to genuinely distinct execution and persist a privacy-safe, allowlisted model-provenance projection; redact evidence values at storage boundaries. This is a design rule and should be verified against the actual dispatch implementation before claiming compliance.