# Architectural Decision Records

One of the most effective ways of documenting architecture decisions is through Architectural Decision Records (ADRs).

{% embed url="<https://adr.github.io>" %}

An ADR consists of a short text file (usually one or two pages long) describing a specific architecture decision.

While ADRs can be writen in plain text, they are usually written in some sort of document format, like Markdown.

ADR format:

{% hint style="info" %}
**ADR**: A short noun phrase containing the architecture decision

**Context**

In this section of the ADR we will add a short one- or two-sentence description of the problem.

**Decision**

In this section we will state the architecture decision and provide a detailed justification of the decision.

**Consequences**

In this section of the ADR we will describe any consequences after the decision is applied, and also discuss the trade-offs that were considered.

{% endhint %}


---

# 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://notebook.iuriioapps.com/architecture-and-design/architectural-decision-records.md?ask=<question>
```

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.