I have been thinking of a knowledge system with two linked guiding principles: 1. Every element is owned by a person. 2. Every element has a “decay rate” or au

I have been thinking of a knowledge system with two linked guiding principles: 1. Every element is owned by a person. 2. Every element has a “decay rate” or automatic time to be trashed. I think this would make it a lot easier to track knowledge in organizations. When something becomes outdated, its owner can just let it die without having to go out and proactively prune every bit of old documentation. When a person leaves the company, his “knowledge items” can be flagged as “soon to not have an owner.” Ultimately I’d actually like to build code projects this way. It probably seems insane to a lot of people to think of the idea of letting little pieces of the code base die and stop functioning, but the benefit I perceive is that our systems would always be tied to some degree to a human understander.