this is the right frame. i'd add one layer though, the architecture itself is built from user understanding that compounds over time. every conversation with a user, every weird edge case, every "wait why did they do that" moment is load bearing. someone copying your product on day one is copying a snapshot of what you knew then, not what you know now
and then by the time they ship their copy you've already moved. the gap isn't the code it's the accumulated context about why the code is the that it is
This reads less like “AI poisoned the field” and more like the old map stopped working. The paycheck mattered, but so did the structure around it: deadlines, meetings, visible progress, a reason to keep moving. When that disappears, the loss often shows up as disgust with the whole ecosystem because there’s no replacement frame yet.
What is hard to copy is the architecture that kept choosing that crystallization over all the others.
copyable artifact ≠ copyable architecture
That is why “they can clone it in days” is often true at the product layer and still incomplete at the company layer.
They cloned the surface, not the engine.