I definitely think about this, but I think some of the concern is a ‘straw man’ issue in that it is built around the idea of an absolute “product” at the end, that revisions live in contrast to.
So the frozen ‘album’ generally isn’t changed. Code, however, exists in a more transient state, and as such revision is built into the concept/model. You don’t hear programmers waxing poetic on if the 3.0 version is “still the same” as the 2.0 because that would sound silly. Sure some features come/go/change, but the it-ness isn’t really part of the discussion. Only the variation-ness.
Music/art, I think, can exist in the same place, but because of historical reasons doesn’t (for the most part). Jazz is a good example of this being the case. “It’s about the singer and not the song”. Sure there are classic/recorded versions, but most jazzers don’t take that as gospel. Each time they play it it is fresh, it is re-imagined, it is re-created, or re-existed.
Glenn Gould even talks about performing Bach stuff this way. Always different, always living.
I guess both of these examples have live-ness in common, though not in the sense that they happen live, but in the sense that they are living things. I should qualify this by saying that I don’t think this is tied to their instrumental/acoustic nature, as the same can happen with other types of thinking/creation, these are just the examples I thought about.
Done-ness, is a whole thing into itself though. And one if the things I love about improv. Done-ness doesn’t come into it. It happened, it’s over. It’s done, by default. <—though that is a cop out