Context engineering asks
What should the model know?
Our thesis is deliberately contestable: situation deserves to become a first-class computational primitive of intelligent systems. The work is to define it, represent it, compare it, remember it, and discover where it holds.
A situation is the meaning of events and state, interpreted from the perspective of an observer, relative to goals, responsibilities, relationships, time, uncertainty, and possible action.
| Event | Something happened. |
|---|---|
| State | Something currently has a condition or configuration. |
| Context | Information is available for interpretation. |
| Intent | An actor wants an outcome. |
| Situation | Those conditions mean something to an observer and establish what response is appropriate. |
An unpaid invoice is one event and one state. For the customer it may be a temporary cash constraint. For the salesperson it may be a relationship risk. For accounts receivable it is a collection responsibility. For the CFO it may signal deteriorating receivables. The facts can be shared while the situations differ.
Context engineering determines what information an AI system receives: prompts, memories, documents, tools, histories, and current state. This is indispensable. But the presence of relevant information does not itself establish what is happening or what responsibility follows.
What should the model know?
What is happening? To whom does it matter? Why now? What is expected next?
Context is material for cognition. Situation is its observer-relative organization into actionable meaning. Modern AI recognizes situations implicitly. Situational AI proposes making that recognition explicit.
Language models operate over tokens. Reinforcement-learning systems often operate over states. Our hypothesis is that intelligent behavior needs a native unit that binds perception, goals, judgment, expectation, action, and outcome: the situation.
Situation is to intelligent behavior what the token is to language modeling. This is an analogy about computational role—not a claim that situations are literal text tokens.
The proposal is not to replace embeddings. It is to change what gets embedded. Semantic embeddings capture similarity in language. A situation representation should capture similarity in underlying dynamics—even when the vocabulary, objects, and domains differ.
A patient disengaging from treatment and a prospect going silent during a sales process share little vocabulary. Yet both may express the same pattern: expected progression has been interrupted, timely intervention matters, and delay increases the probability of failure.
If a latent situation space can preserve such structure, experience may transfer across domains wherever the situational dynamics are analogous.
Interpretation is essential. Detecting an event is not the same as recognizing the situation. A situation-centric architecture maintains an explicit hypothesis about what is occurring, revises that hypothesis as evidence changes, selects a response, and observes whether the response produced the expected transition.
Conventional memory remembers information. Situation memory remembers experience: what occurred, what was recognized, from whose perspective, what response was selected, why it was selected, what outcome followed, and whether the original interpretation was correct.
SCBCM—the Situation-Centric Bot Cognitive Model—is one proposed implementation of this larger thesis.
What is the minimal situation representation? Which properties are invariant, temporal, observer-relative, or learned?
Can a system detect emerging and overlapping situations—and recognize when its interpretation is wrong?
Can situational retrieval find useful structural analogies that semantic retrieval misses?
Can a system accumulate situational experience and improve without merely accumulating more text?
Does an explicit situation layer improve timing, decision quality, coordination, adaptation, and explanation?
Which situational patterns transfer across coding, operations, education, care, and collaboration?
During the summer of 2026, five UT Dallas students worked with Mindspace AI to explore different questions emerging from Situational AI: its theoretical foundations, its relationship to existing models of situation awareness, whether explicit situation recognition can reduce computational context, and working applications built on situation-centric concepts. Each has a permanent page here, and all five are presented together at the October 22, 2026 forum.
Krishang Reddy Mandala — Evolution of the idea, related models and Endsley’s Situation Awareness framework.
Research in Progress
Sabareesh Dinakaran — Situation recognition, context reduction and smaller models.
Research in Progress
Sai Jagadish Manchikanti — Applying situation recognition to emerging organizational risk.
Experiment
Yuvan Muruganandham — Exploratory application and live demo.
Experiment
Avani Tripathi — The journey, questions and lessons emerging from the summer work.
Research in Progress
Situational AI is an open research initiative. We invite researchers, engineers, cognitive scientists, designers, operators, and critics to contribute definitions, architectures, datasets, experiments, implementations, and counterarguments.