I typically write up all of that in my documentation somewhere. Stuff like "first thoughts are this approach might work, talked to person who had this idea, loo

I typically write up all of that in my documentation somewhere. Stuff like "first thoughts are this approach might work, talked to person who had this idea, looked at this link and found this info, decided to go with this approach because of factors x, y, z". This isn't the primary user-facing documentation but a subpage or something that's helpful a couple of years down the line It's like a book titled "A History of [Object]" that traces what solved problems before the object, issues with old solutions, the emotional, financial, etc state of the inventor, why they chose this solution over that one, how the object was adopted and improved afterwards, other inventions spawned off the object, etc. Capturing the history of the object requires capturing the context around the object too