Architecture decision records¶
Each record explains one decision that shapes how the library behaves: the context, what was decided, the alternatives that were rejected and why, and the consequences. They are the reasoning behind the rules in the user guide; read one when a behaviour looks surprising.
A record is never rewritten to match a later decision. A new record supersedes it, so the history of why the library works this way stays readable. The architecture overview shows where each decision lives in the code.