> For the complete documentation index, see [llms.txt](https://bdi.gitbook.io/bdi-public-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bdi.gitbook.io/bdi-public-documentation/readme/introduction/stack-and-kits.md).

# Stack and KITs

## 1. BDI Stack and KITs

To assist the creation of applications according to the architectural principles, BDI defines a set of *building blocks.* Each building block provides tools and guidelines to implement parts of the required functionality. The building blocks are shown in the BDI stack:

<figure><img src="/files/ewfcNDZ86v5XazwlI4Ye" alt=""><figcaption><p>Building blocks of BDI</p></figcaption></figure>

Implementation of the principles by means of parts of the stack is aided by the definition of **KITs**. A KIT is a subset of the BDI stack that forms a coherent capability. Implementing a KIT makes it easier to start with a minimal viable subset and add additional functionality later as the need for it arises.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://bdi.gitbook.io/bdi-public-documentation/readme/introduction/stack-and-kits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.