Avoiding catastrophic forgetting in a continually-updating model depends on per-parameter step-size optimization driving continual backprop, not on data replay or freezing layers. The update rule itself is the primary defense against knowledge destruction.
If forgetting is primarily a step-size/update-rule problem, engineers building online or deployment-time learning can target the optimizer and per-weight plasticity rather than building large replay buffers or periodic full retraining, which changes memory, latency, and storage budgets.
Any system that mutates its own parameters at runtime (online RL, adaptive rankers, personalization) should treat per-parameter learning rates and plasticity control as a first-class subsystem, decoupled from the raw gradient computation.
Continual backprop combined with ongoing generate-and-test can maintain and expand knowledge.
Continual learning requires step-size optimization and continuous experiential feedback loops.