Building a culture of architectural decision records (ADRs)

we recently adopted Architectural Decision Records (ADRs) on our team, and it's been pretty transformative for documenting why certain choices were made. it's helped us onboard new engineers faster and avoid rehashing old debates. however, getting consistent buy-in and making sure they're lightweight enough not to become a burden has been a challenge. we're trying to integrate them into our PR review process. what are your best practices for building a strong culture around ADRs? specifically, how do you decide what truly qualifies as an 'architectural decision' worthy of an ADR versus a regular design doc or just a comment in code? any tips for keeping them concise and actionable?