Context as a Design Requirement
An early research direction on situated AI systems in development contexts.
Research question
What changes when development context is treated as a design requirement from the beginning rather than a constraint to accommodate later?
This stream explores contextual AI systems in low-resource settings and the possible role of low-resource language work. Specific field sites, partner organizations, and language projects have not been supplied or claimed.
A starting position
The relevant questions may concern connectivity, institutions, language, local knowledge, and the authority to define a useful outcome. Which of these matters must be learned in the setting rather than assumed in advance.
Methods to develop
An eventual project should identify a concrete setting, engage the relevant people in defining the problem, and specify how the system’s use would be evaluated. No field study or deployed system is reported here.
Open questions
How can a system remain useful when connectivity is intermittent? Who can correct its interpretation of local context? What evidence would show that the system supports a decision rather than merely producing plausible advice?
The notes on context and local knowledge connect this direction to the epistemic agency stream.
Results & artifacts
This is an exploratory research direction. There are no empirical results, released datasets, or publication records linked yet.
Connected thinking.
Related reading 2
Context is a design requirement, not a personalization layer
AI for developmentLocal knowledge is not just another input field
AI & epistemic agencyLinked from 3
Backlinks from declared content relationships.
EssayLeaving room for judgment ↗NoteContext is a design requirement, not a personalization layer ↗NoteLocal knowledge is not just another input field ↗