Most teams that adopt ADRs write down what they chose and stop there. That is the least useful half.

Write the context like a witness statement

Record what was true at the time: the team size, the deadline, the thing you did not yet know, the option you rejected and why. A future reader who finds "we chose Kafka" learns nothing. One who finds "we chose Kafka because we expected replay to matter and we had one engineer who had run it" can check whether either of those still holds.

Keep them short, keep them in the repository, and never edit one after it is accepted. Supersede it with a new record instead — the trail of reversals is the most instructive document a codebase can have.