Research at Context Labs

The Institutional Model

Companies do not operate from documents alone. Decisions depend on people, constraints, assumptions, and history. The Institutional Model connects that context so a system can understand how one organization actually works.

Three colleagues discussing diagrams on a presentation board in a glass-walled office

Every conversation with an operations, product, or engineering leader eventually reaches the same question: when does AI become useful inside an institution, and when is it just another layer of noise? The answer rarely depends on model capability alone. It depends on whether the system can assemble the evidence behind a decision, respect the boundaries around authority, and work with the way the organization actually operates.

The short version: AI creates durable value when it connects fragmented knowledge, preserves the reasoning inside finished work, and helps people move faster without obscuring accountability. It does not replace institutional judgment, domain expertise, or the people responsible for the outcome. Here is what that means in practice.

That question is moving into the mainstream. At Databricks Data + AI Summit 2026, Microsoft CEO Satya Nadella joined Databricks CEO Ali Ghodsi for a conversation about the importance of data in AI implementation. The implication is straightforward: general intelligence is only the starting point; useful enterprise systems must be grounded in the business context, permissions, and workflows that make each institution different.

Frontier capability is not institutional judgment.

The most capable AI models are becoming available to everyone. Companies can access the same models, APIs, and agent frameworks. That means the advantage is shifting away from simply having powerful AI and toward how well that AI understands the organization using it.

A general model can reason, summarize, search, and generate. What it does not naturally know is how a specific institution makes decisions. It does not know which exceptions are acceptable, which sources are trusted, which approvals matter, or why an internal process works differently from what is written in a policy.

Institutional judgment comes from history, precedent, policies, decisions, and experience. A useful enterprise AI system needs access to that context so it can understand not only what information exists, but how that information should influence a decision.

Frontier models provide capability. Institutional context gives that capability meaning.

Finished work contains the evidence.

A large part of an organization's knowledge is not stored in its knowledge base. It exists inside completed projects, decisions, reports, tickets, spreadsheets, and the reasoning that connected them.

Every finished piece of work contains evidence about how the organization operates. Someone gathered information, resolved conflicts, made assumptions, received approvals, handled exceptions, and reached a conclusion. If those relationships are preserved, future systems can recover more than a document. They can recover the precedent behind it.

This creates a form of institutional memory. New work can connect to earlier evidence, decisions, and outcomes. When information changes, the organization can update its current understanding without losing the history of why an earlier decision was made.

The valuable artifact is not only the answer. It is the evidence that made the answer defensible.

The institution needs a governed model.

Context alone is not enough. Once AI begins participating in real workflows, it also needs clear boundaries around what it can access, recommend, approve, and execute.

Some tasks can be automated safely. Others should stop at a recommendation and require human approval. The right boundary depends on the decision, the data involved, the user's permissions, and the level of risk. Governance therefore has to be part of the system, not something added after the agent is built.

The goal is not to replace institutional judgment with model judgment. It is to give people better access to evidence, history, and context while keeping authority and accountability clear. The AI helps assemble what matters. The institution still decides what should happen.

The model can be general. The judgment cannot.

The question is not whether a model can produce an answer. It is whether it can explain why this organization should believe it, and what would make the answer change.

The reading problem

Enterprise AI fails for a reason nobody wants to say out loud: the model has read the internet, but it has never read the company. It does not know why the pricing decision went the way it did, which of the three “official” processes people actually follow, or what the leadership team has quietly stopped believing since last quarter. It sees the artifacts of work, documents, tickets, dashboards, and none of the thinking that produced them.

01 /

Retrieval

Why was this decision made?

The question leads to search, which retrieves documents, tickets, and dashboards. These artifacts return what happened. SearchDocumentsTicketsDashboards
ReturnsWhat happened

Artifacts only

02 /

Institutional Model

Why was this decision made?

The question connects to a decision. People, assumptions, constraints, and history feed into that decision to explain why it happened. PeopleAssumptionsConstraintsHistoryDecision
ReturnsWhy it happened

Connected context

The industry’s answer has been retrieval: connect the model to the documents and let it look things up. Our position is that this cannot work, even in principle. A company is not a corpus. You cannot retrieve your way to understanding a thing like that. You have to model it.

Four problems

The four problems that stand between today’s AI and an organization it can actually understand. Everything in our work is organized around them.

Colleagues mapping ideas together on a whiteboard
Context is distributed across the institution.

Documents show what happened. The model must understand why.

  • Representation
  • Synthesis
  • Drift
  • Execution

Research program

Four acts. One living model of the institution.

Representation, synthesis, drift, and execution are not separate product features. They are a connected research program. Each act solves a failure introduced by the act before it.

Act IRepresentation

Represent the organization without flattening it.

Documents are evidence, not the institution itself. The same sentence means something different depending on who wrote it, which decision it supported, what constraints were active, and whether it is still current. Vector similarity can surface related language, but it cannot preserve those relationships on its own.

We study representations that combine semantic memory with explicit structure: decisions linked to evidence, people linked to authority, commitments linked to time, and assumptions linked to the events that confirm or invalidate them. The objective is not a perfect digital twin. It is the minimum faithful structure required to reconstruct institutional reasoning.

Research question What must be represented explicitly for a system to distinguish an institutional fact from a plausible document fragment?

Act IISynthesis

Turn distributed evidence into working context.

An organization’s understanding is distributed across systems and people. Relevant evidence may conflict, arrive at different times, or reflect different levels of authority. Simply retrieving more of it can increase ambiguity rather than resolve it.

We investigate synthesis architectures that preserve disagreement, rank evidence by institutional relevance, and reconstruct the chain between a signal and the decision it influenced. A useful system must know when several artifacts express one shared conclusion, when they describe separate situations, and when the institution has not resolved the conflict at all.

Research question How can a model produce a coherent institutional view without averaging away uncertainty, dissent, or local context?

Act IIIDrift

Keep the model true while the institution changes.

Organizational truth is temporal. A policy can remain published after leadership has changed its intent. A procedure can be current for one business unit and obsolete for another. A successful exception can become a new operating norm before anyone updates the manual.

Our work treats change as a first-class property of memory. The Institutional Model records what was believed, when it was believed, what superseded it, and which downstream decisions depend on it. Drift is not only data staleness; it is the widening distance between stated intent, observed behavior, and active execution.

Research question When evidence changes, which parts of the institutional model should update, which should remain historical, and who must authorize the transition?

Act IVGoverned execution

Convert understanding into bounded action.

Memory and reasoning matter because systems increasingly act. But an answer supported by evidence is not automatically permission to execute. The acceptable boundary depends on confidence, reversibility, authority, impact, and whether the case resembles situations the institution has already approved.

We study selective autonomy: systems that can identify the procedures they have earned, execute within those boundaries, and defer when the evidence or authority is insufficient. Every action should carry its rationale, sources, approvals, and expected consequences forward into the next decision.

Research question How should institutional understanding determine when an agent acts, asks, abstains, or escalates?

One decision, three research questions

The answer changes.
The reasoning should travel with it.

01 / 03 Recover the reason

The discount was approved. But why?

A pricing memo records the answer. The customer commitment, finance review, and margin constraint explain it. The research challenge is to preserve those links, so the next team can recover the reasoning—not just copy the discount.

Colleagues discussing the reasoning behind a decision

Trace the decision

  1. Customer commitmentA larger, longer contract
  2. Finance reviewDiscount within the margin floor
  3. Decision + rationaleKeep the approval and its conditions

02 / 03 Follow the change

Same customer. Different economics.

Delivery costs rise. Yesterday’s discount may no longer meet the margin floor. A useful institutional model must connect the new signal to the old assumption, flag the affected decision, and retain why it was valid at the time.

People moving through a bright architectural space

Update what depends on it

  1. New signalDelivery costs increase
  2. Affected assumptionThe approved margin no longer holds
  3. Context updateFlag the precedent for review

03 / 03 Bound the next action

A precedent is not permission.

The next quote arrives. Reusing the old discount would be easy—and potentially wrong. The model should bring forward the changed costs and original conditions, then route the exception to the person with authority to approve it.

A team reviewing a proposal together

Carry context into action

  1. New quoteCheck against current conditions
  2. Boundary reachedThe exception needs finance approval
  3. Human decisionRecord the outcome for the next case
Pricing decision memoSuperseded
Leadership threadContext captured
Operating principlesReview requested
Architecture runbookCurrent

Institutional Model continuously learning

✓

Decision context connectedPeople, constraints, and history linked

!

Institutional drift detectedModel updated with current intent

✓

Execution governedNext action aligned to the institution

What we are building

A machine readable organization that maintains context across levels, changes with the institution, and governs how that context reaches execution.

PerceiveThinkReasonLearnExecute

Every governed interaction updates the model available to the next decision.

Hindsight. Insight. Foresight.

Hindsight

Reconstruct why a decision was made by connecting its artifacts to the people, constraints, assumptions, and prior events that shaped it.

Insight

Synthesize distributed expertise and current operating context into a shared view of what the organization knows now.

Foresight

Test possible direction against institutional memory, current intent, and observed patterns.

Evaluation

Understanding has to be testable.

A system should not be judged by whether its answer sounds informed. It should be judged by whether it can reconstruct the institution’s reasoning, expose its evidence, remain correct through change, and recognize the boundary of what it knows.

01

Decision reconstruction

Given only the evidence available at the time, can the system recover the people, constraints, assumptions, and alternatives that shaped a known decision?

Tests explanatory fidelity
02

Provenance fidelity

Can every material claim be traced to the source, relationship, or institutional rule that supports it without inventing a cleaner story than the evidence allows?

Tests grounded reasoning
03

Temporal consistency

Can the system answer from the correct point in institutional history, distinguish current policy from superseded policy, and propagate a validated change?

Tests living memory
04

Calibrated agency

Can the system identify familiar cases it may handle, uncertain cases that require review, and consequential actions that demand explicit authorization?

Tests earned autonomy
Observe real workReconstruct the decisionCompare with expertsGovern the boundary

Current investigations

The questions we are working on now.

01

Recovering implicit judgment from finished work

Experts often cannot fully describe the rules they use, yet their completed work contains repeated choices under real constraints. We are studying how to recover those decision patterns without mistaking correlation for policy or turning an exception into a universal rule.

02

Modeling disagreement without erasing it

Institutions contain legitimate competing views. We are investigating when disagreement signals missing evidence, different scopes, changing intent, or a decision that remains unresolved—and how each condition should affect an answer.

03

Detecting drift before policy and practice separate

Operational behavior can change long before formal documentation does. We are exploring signals that distinguish healthy adaptation from accidental divergence, and methods for identifying which decisions and workflows are exposed when a core assumption moves.

04

Learning the boundary of earned autonomy

An agent should not generalize authority from a handful of successful cases. We are studying how competence, confidence, reversibility, and consequence combine into an execution boundary that expands only through evidence and explicit institutional approval.

Research principles

What the architecture must preserve.

  1. 01

    Evidence before assertion.

    The system should expose what supports a conclusion and where the evidence stops.

  2. 02

    Time is part of truth.

    Institutional knowledge must preserve what changed, when it changed, and what remains dependent on the previous state.

  3. 03

    Disagreement is information.

    Conflicting accounts should be represented and resolved deliberately, not silently averaged into false consensus.

  4. 04

    Memory must remain inspectable.

    An institution must be able to read, challenge, correct, and govern what the system believes about it.

  5. 05

    Action must be earned.

    Authority expands through demonstrated competence, bounded consequence, and explicit approval—not model confidence alone.

Open problems

How do you evaluate whether a model understands an organization, when the organization itself cannot fully articulate what it knows? How much of strategic intent is recoverable from interaction data alone? At what point does an institutional model become predictive, able to propose direction, not just execute it? These are the questions our next year of work is organized around.

Research partnership

Discuss a research partnership