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 for more information.

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.

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.