Freeing memory and forgetting configuration are separate actions.

Lizard records the last stopped model, runtime provider, and relevant profile state after release is proven. That gives the operator a defined restart path without claiming the model remained resident.

Lifecycle state becomes easier to reason about when 'stopped', 'restartable', and 'loaded' are distinct.

What state should survive when you unload a local model?

Engineering fact: Lizard's model lifecycle retains restartable metadata for the last stopped model and provider so an intentional stop can be reversed without rediscovering the configuration from scratch.

Read the relevant Lizard page

#LizardNative #LizardLLM #LocalAI #GGUF #InferenceEngineering

<!-- lizard-marketing-slot:day-24-pm -->