How do you capture WHY engineering decisions were made, not just what?

We onboarded a senior engineer recently strong, 8 years experience. He spent 3 weeks playing code archaeologist just to understand WHY our codebase looks the way it does. Not what the code does. That ...