# Architecture Decision Records [Architecture Decision Records](https://github.com/joelparkerhenderson/architecture-decision-record) (ADRs) are concise documents that capture important architectural decisions made during the lifecycle of a software system. Each ADR focuses on a single decision, detailing the context, the decision itself, the alternatives considered, and the consequences of the chosen approach. They are critical for maintaining architectural clarity, especially in complex or long-lived projects where decisions can outlast the original developers. By documenting the rationale behind architectural choices, ADRs promote transparency, enable easier onboarding of new team members, and help avoid repeating past mistakes. They also support better communication across teams by providing a lightweight, structured way to preserve architectural knowledge over time. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.defguard.net/1.5/in-depth/architecture-decision-records.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.