Context Intelligence

Context infrastructure
for AI agents.

Give every AI agent the context it needs for the task, including relevant history, relationships, boundaries, changes, and human decisions, before it acts.

Watch one task

One task, start to finish.

What GammaLex read, what it picked, what it found wrong, and why it stopped the agent.

GammaLexGammaLex AIContext / Runs / RUN_8F92AB
YK

Context Run

RUN_8F92AB

Evaluate whether transaction #3812 has sufficient context for the requested decision.

BLOCKED

Sep 8, 2026 · 10:24 AM

Requested by
finance_agent_prod
Via
SDK
Environment
Production
Scope
transaction:3812

Context selected

17 of 2,481 permitted records across 5 sources

  • Financial activity6
  • Accounting records4
  • Applicable rules3
  • Prior decisions2
  • Supporting evidence2

Readiness

Blocked

Context is not ready for autonomous execution. Required supporting evidence is missing.

Findings

3
  • ×MISSINGRequired supporting evidence was not found.
  • ×CONFLICTINGTwo sources disagree on classification.
  • !CHANGEDApplicable policy changed after the underlying record was created.

Next steps

  1. 1Review missing evidenceSee required documents
  2. 2Check source permissionsVerify access to supporting records

Built with trusted partners across research, industry, and public innovation.

Start from the task

Tell GammaLex what the agent is trying to do, who is acting, and the scope of the request. GammaLex determines which permitted context matters.

Developer

from gammalex import GammaLex

glx = GammaLex()

context = glx.get_context(
    task="Evaluate whether transaction #3812 has sufficient context...",
    actor="finance_agent_prod",
    scope={"id": "transaction:3812"},
)

Returned context

17 of 2,481 permitted records selected

3 findings

  • Missing evidence
  • Conflicting classification
  • Policy changed

Readiness

BLOCKED

View context package →

Gather what matters

From thousands of permitted records, GammaLex selects what matters to the task and preserves why each piece of context belongs.

Context — 17 of 2,481 selected

Transaction #3812

PostgreSQL

Why selected

Primary object referenced by the task.

Relationships

  • Invoice #8831
  • Vendor #220
  • Classification TAX-14

Provenance

transactions.3812

Retrieved

Sep 8, 2026 · 12:04 AM

Check whether the context is ready.

GammaLex detects missing, conflicting, changed, uncertain, or out-of-bounds context before the agent relies on it.

Findings

3 findings · BLOCKED

MISSING

Readiness impact: BLOCKED

Required supporting evidence was not found.

Expected

Supporting documentation

Related context

  • Transaction #3812
  • Invoice #8831

Impact

Required before autonomous execution.

Why this matters

This task depends on evidence that is not currently present.

Hand it back with the reasons

Return the selected context with readiness, findings, evidence, provenance, and the reasons behind the result.

Context Package

CP_826103

Result

BLOCKED

17 context records · 3 findings · 5 sources

Returned to agent

Context

17 selected records

  • Transaction #3812
  • Invoice #8831
  • Applicable Policy

+2 more

Readiness

BLOCKED

Context is not ready for autonomous execution. Required supporting evidence is missing.

Findings

  • Missing evidence
  • Conflicting classification
  • Policy changed

Sources 5·Provenance Complete·Trace 174ms

Everything an agent needs to understand the task before it acts.

Developed and tested against real work — patent intelligence alongside a practicing attorney at KPPB Law, and clinical intelligence through GammaLexCare.

Gathering context

For one job, gather the records it depends on, how they connect, what came before, and the reason each was picked.

  • 01Transaction #3812Primary object referenced by the task.
  • 02Invoice #8831Linked to the transaction as its supporting invoice.
  • 03Applicable PolicyApplicable to classification TAX-14.

Built where context has consequences.

GammaLexPatent and GammaLexCare are applications of GammaLex Context Intelligence, and the proving grounds where it is developed and tested against real work.

GammaLex Context Intelligence

Independent and concierge practices

GammaLexCare

Show up to every visit already knowing.

GammaLexCare carries prior visits, care plans, patient-reported changes, and provider-approved decisions into the conversation happening now — and says what is still missing while there is time to ask.

What it connects

  • Prior visitsLongitudinal
  • Care planCurrent
  • Patient-reported changeSince last visit
  • Provider decisionsApproved
Explore GammaLexCare

Patent work

GammaLexPatent

Context Intelligence for patent work.

GammaLexPatent connects the pending claim set, cited prior art, prosecution history, and amendments around the patent task being performed.

What it connects

  • Pending claim setIncl. amendments
  • Cited prior artPer claim
  • Prosecution historyWhat was surrendered
Explore GammaLexPatent

OpenContextually

In development

Open context for every agent.

GammaLex's open-source context layer answers one question for a coding agent: which files should it read before it starts working on this task? It never edits anything. It hands the agent a reading list.

It is the same idea GammaLexPatent and GammaLexCare apply to a patent file and a patient chart — proven first on code, where the connections between things are already written down.

  • No LLM
  • No network
  • One dependency
  • Deterministic
  • Sub-second
View on GitHub
  1. 01Rank what matters.

    Every file it is allowed to open is scored against the job — the name first, then what is defined inside it, then the text. Saying a word two hundred times does not win.

  2. 02Follow the relationships.

    Having found one file, it follows what that file depends on — and pulls those in too, even when they never mention what you searched for.

  3. 03Send only the relevant part.

    Not a list of filenames, which makes the agent go read everything. Not whole files, which fill up its memory. Just the lines that earned the file its place — with anything secret stripped out.

  4. 04Stay quiet when unsure.

    Its checks say nothing rather than guess. On four real codebases, neither one spoke up — which is right, not a gap.

Why I Built GammaLex

Yen Kha

Founder, GammaLex

Why We Exist

GammaLex did not begin with a product category.
It began with a standard I was no longer willing to compromise.

If AI is going to influence decisions that matter, it should not act on whatever information happens to be available. It should understand what came before, what changed, what remains uncertain, and where human judgment belongs.

That is why we are building Context Intelligence at GammaLex.

Give your agents the context to act responsibly.

Build with GammaLex or help us test Context Intelligence in real work.

Book a walkthrough