I just heard good things about Layered Architecture, mixed things about Microservices and used to swear by MVC years ago. Does it always "it depends" or is there one that can't go wrong?
RFCs is another type of technical decision making documentation that has been popular for decades now, and can probably be found more widely as it's more spreadout online from what I can tell. It's worth pointing out that RFCs are less easier to locate it next to specific implementations, since it focuses heavily on a more abstract type of standardization and specification document, and lives further away from the code than ADRs for example.
All of that to say if the intent is to track down code historial evolution, some types of RFCs out there _might_ help shed some facet of the light you may be looking for.
Although I have no experience with any in particular, the experts I know are leaning towards the apparently most complete, mature and robust solution which we concluded to be AWS API Gateway, which in my view has an extremely high fidelity that's hard to reason against (though I'm looking forward to be proved wrong).
AWS API Gateway might probably have its own complexities and depending on what you're solving for specifically, might be way too much to take. But make no mistake, the knowledge you and your team will acquire is likely to payoff in the long run since I think it'll likely span across decades and continue to develop faster than most of its competitors. Though to be clear, I'm also for giving smaller businesses a fair shot.