A Contextualization is a Problem viewed through a specific combination of Actor and/or Context. It’s the core unit of insight in Kontext.Documentation Index
Fetch the complete documentation index at: https://getkontext.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Why Contextualizations matter
Consider a Problem like “Order tracking is unreliable.” On its own, that’s a generic statement. But when you see it broken down:| Context | Actor | What it means |
|---|---|---|
| Multi-location retail chain | Store Manager | Tracking breaks down across locations, making inventory reconciliation impossible |
| Commuting / on the go | Delivery Driver | Real-time tracking is essential but drops out in areas with poor connectivity |
| Large enterprise with dedicated IT | Operations Lead | The tracking API doesn’t expose enough data for their internal dashboards |
The Contextualization matrix
On a Problem’s detail page, Kontext shows a matrix of Contexts (rows) and Actors (columns). Each cell that has data represents a distinct perspective on the Problem. This matrix is what makes Kontext different from a summary. Instead of “10 people mentioned onboarding issues,” you see exactly which Actors, in what Contexts, and how their perspective shapes the Problem differently. Each cell links back to the specific pieces of Feedback that produced that Contextualization. You can always trace a detection back to its source — proofread the original text, verify the analysis, and understand the Problem in its full depth.How Contextualizations build up
Contextualizations aren’t created manually. They emerge automatically as Feedback is analyzed:- New Feedback arrives
- A Problem is detected (or matched to an existing one)
- The Actor and/or Context are identified
- If this Actor/Context combination hasn’t been seen for this Problem before, a new Contextualization is created
- If it has, the existing Contextualization is enriched with the new Feedback