Research Map
Ax is a practical library, but its shape is not accidental. The core ideas line up with a serious LLM systems lineage: declarative model programs, signatures, constraints, reflective optimization, runtime-backed long-context work, and persistent context maps.
This page is not an endorsement wall. It is a map from public research ideas to the Ax concepts users see in the docs.
Authors: Omar Khattab, Arnav Singhvi, Paridhi Maheshwari, Zhiyuan Zhang, Keshav Santhanam, Sri Vardhamanan, Saiful Haq, Ashutosh Sharma, Thomas T. Joshi, Hanna Moazam, Heather Miller, Matei Zaharia, Christopher Potts.
Year: 2023.
Why it matters for Ax: DSPy makes LLM pipelines declarative and optimizable. Ax carries that idea into typed signatures, generated structured outputs, examples, evals, and multi-language package surfaces.
Authors: Arnav Singhvi, Manish Shetty, Shangyin Tan, Christopher Potts, Koushik Sen, Matei Zaharia, Omar Khattab.
Year: 2023.
Why it matters for Ax: Assertions show why constraints should be part of the program, not just comments in a prompt. Ax uses signature fields, schemas, validators, retries, and parser feedback to keep outputs usable.
Authors: Lakshya A. Agrawal, Shangyin Tan, Dilara Soylu, Noah Ziems, Rishi Khare, Krista Opsahl-Ong, Arnav Singhvi, Herumb Shandilya, Michael J. Ryan, Meng Jiang, Christopher Potts, Koushik Sen, Alexandros G. Dimakis, Ion Stoica, Dan Klein, Matei Zaharia, Omar Khattab.
Year: 2025.
Why it matters for Ax: GEPA uses natural-language reflection and a Pareto frontier to optimize prompts and multi-component AI systems. Ax exposes this as practical optimization for generators, flows, and agents.
Authors: Alex L. Zhang, Tim Kraska, Omar Khattab.
Year: 2025.
Why it matters for Ax: RLMs treat long prompts as an external environment the model can inspect and decompose. Ax agents follow the same spirit by keeping durable state in the host runtime and letting the model work through bounded, tool-mediated turns.
Authors: Zhuohan Gu, Qizheng Zhang, Omar Khattab, Samuel Madden.
Year: 2026.
Why it matters for Ax: PEEK frames context maps as persistent orientation knowledge for recurring long-context work. Ax agent docs use the same product instinct: memory, context maps, skills, and runtime summaries should keep agents oriented without replaying every token.
How Ax Uses This Lineage
Ax focuses these research ideas into a developer library:
- Signatures make model calls declarative.
- Field constraints and schemas turn output parsing into a program contract.
- Tools, MCP clients, and child agents turn external systems into typed capabilities.
- Agent runtime state keeps long-running work out of the prompt transcript.
- Optimizers tune programs against examples, metrics, and judges.
- AxIR keeps these concepts portable across native package surfaces.
The result is not a paper clone. It is a library for building and operating real LLM applications with the best parts of this research line made practical.