I used to think progress had only one direction.
Install the update.
Replace the old version.
Move on without looking back.
Most software quietly teaches that habit. The latest release is the only one that matters, and everything before it fades into an archive nobody opens again.
One detail in OpenGradient's Model Hub doesn't work that way. Every model version gets its own Blob ID — major.minor, never overwritten, never folded into the next release.
Didn't think much of it until I looked at what that means for a version that didn't make the cut. It's still there. It just stops being the one anyone points to.
So improvement isn't always about replacing the last answer. Sometimes it's about keeping the path that got you to this one, including the parts that aren't the latest thinking anymore.
An old version can stop being current without turning into nothing.
Most products just don't let you see that. Which is probably why progress feels like a straight line when it's mostly not.
Makes me wonder if keeping old decisions visible is just versioning, or something closer to how progress actually works.
#OPG @OpenGradient $OPG