I've wanted a way to track the full context in which code was written or updated for years now. This would track and save all resources that were accessed as e

I've wanted a way to track the full context in which code was written or updated for years now. This would track and save all resources that were accessed as events. I mean online and offline documentation, specs, pdfs, architecture diagrams, code examples and other parts of the codebase, Jira tickets, bug reports, application screens and output, tests run, failing tests, compiler errors and emails. Everything that the human took in as input before outputting that code. What was Bob looking at when he wrote this line of code? If you had been sitting next to him that week, what would you have seen? When looking at code, a recommendation engine would show that context, using event data and view frequency to compute relevance. To do this properly would likely need an isolated developer environment separate from any personal use. Another option would be some kind of ML that would filter out irrelevant events or give the developer a chance to manually edit this data at commit time. A simplified version of this would track the web resources accessed and allow the developer to manually insert additional links, notes and documents. This is a tool I would pay for. Call it Retrace.