# Business Context

Outside of the structured data and relationships, its important to capture things like metrics, calculations, acronyms, and other details / implicit knowledge pertaining to the data scoped for the Knowledge Base. This is referred to as "Business Context".

See our primer [here](/setting-up/configure-knowledge-base/add-business-context.md) for more information.

{% hint style="info" %}
Business Context is incredibily powerful and represents one of the many ways you can embed knowledge into Lumi AI. In general, you should put the minimum knowledge necessary to address the insights and scope of the Knowledge Base rather than add large volumes indefinitely to this section. "Less is often more" rings true for this section.
{% endhint %}

## Key Components

In this section, one can either add, modify, or remove business context.

Each line item should have reasonable labels, types, and definitions associated with each. See further considerations below for tuning.

## Considerations

Business Context is highly flexible, but there are some good practices to keep in mind:

* Title lines appropriately so they get proper relation to a user's prompt or other context
* Keep the context itself concise. Rephrase if necessary, otherwise lengthy context may be "washed-out"/diluted or outright ignored in the workflow.
* Instructions/patterns work better than hard code. The reason being that the code itself may shift or be inaccurate in certain contexts, whereas instructions are more flexible and less sensitive to being applied "as-is" across prompt scenarios.


---

# 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.lumi-ai.com/product-features/knowledge-base/business-context.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.