How does Refold respond to Karpathy on disposable code?

Refold agrees with Karpathy that code is becoming disposable — and pushes the idea one beat further: if code can be regenerated, then code isn't the asset anymore. What survives is the reasoning behind the decisions.

Refold's context graph captures exactly that — how an enterprise's systems behave and why decisions were made. The disposable-code narrative doesn't threaten Refold; it points directly at the layer Refold owns.