I find that backlog items get reframed into other stuff too. I like having a history of them is an itemized list of things that lead to decisions. Is the only p

I find that backlog items get reframed into other stuff too. I like having a history of them is an itemized list of things that lead to decisions. Is the only point to have a list of your absolute decisions and context that lead to the things included current product? Like some sort of psychotic performative minimalism? A lot of times a decision is to not do something at that time. In my experience, the most important things involved in building a software product is what you decide not to do. The backlog is a knowledge base of how those decisions are made. They can be archived as needed. Decision points can be made referencing them. A year or three later when the same problem crops up, sometimes under a different name, you've got information about it. Maybe it's time. So now you have that knowledge sitting there to help new decisions.