A provider selector is meaningless if the runtime silently launches a different engine.

Lizard carries the requested provider through server launch, health checks, benchmark artifacts, onboarding activation, and Chat telemetry. A mismatch is treated as an error rather than a successful run under the wrong label.

Provider identity belongs in both execution and evidence.

Can you prove which engine served the last response in your local stack?

Engineering fact: Lizard exposes lizard-native and Caterpillar as separate runtime providers in serve, onboarding, benchmark, and Chat paths instead of silently substituting one for the other.

Read the relevant Lizard page

#Caterpillar #LizardLLM #GPUProgramming #LocalAI #GGUF

<!-- lizard-marketing-slot:day-18-am -->