Why AX Framework exists
Digital products have a new kind of user. AX Framework is an attempt to give the people who build those products a shared, practical way to design for it.
The shift
For most of the history of software, the user on the other side of an interface was a person. That assumption shaped everything: navigation, layout, error messages, confirmation dialogs, even the idea of a session.
AI agents change the assumption. They browse, compare, fill in forms, and complete purchases on behalf of people. They are capable but literal. They don't share our visual conventions, they can't read meaning from a layout, and they need to be certain before they act on someone's behalf.
Today most products serve agents by accident. Agents scrape what they can and guess the rest. Sometimes it works. When it doesn't, the failure is often invisible: a misread price, a duplicate order, a task reported as done that never happened. People bear the consequences, and they rarely know why.
We think this is a design problem, and that it deserves the same care the industry learned to give human experience. That means principles, patterns, a shared vocabulary, and honest evaluation.
What AX is, and isn't
AX Framework is a design framework: a structured way of thinking about how agents discover, understand, act, and recover. It points to established standards such as semantic HTML, schema.org, OAuth, and HTTP, and to open protocols such as MCP, wherever they already solve part of the problem.
It is not a standard. It has not been ratified by any standards body, and nothing here should be read as a claim of industry adoption. The formats in the documentation are proposals and examples. We would rather be useful and revisable than authoritative and wrong.
Long-term vision
In the long run, we hope agent experience becomes an ordinary part of product work, the way accessibility and responsive design did: something every team considers, with known patterns and shared ways to measure it.
Concretely, that means:
- A stable set of principles and patterns, refined by real implementations.
- Evaluation methods that teams trust, including tools that automate parts of it.
- A body of research on how agents actually behave against real products.
- Agents that act on people's behalf safely, accountably, and in ways those people can see.
None of this exists yet at maturity. It is the direction, not a description of the present.
Principles of the project
- Human-centered. Agents act for people. AX succeeds only if those people are better off.
- Honest about status. Every page distinguishes proposals, established standards, roadmap items, and available functionality.
- Practical over complete. A pattern that one team can apply this week beats a taxonomy no one uses.
- Never at the expense of accessibility.
Open collaboration
How to contribute
AX Framework is early. There is no established community or governance yet; the first contributors will shape both. These are the kinds of contribution that help most.
Propose a pattern
Describe a recurring problem, the context, and a solution you have seen work. Include an interaction diagram and an example if you can.
Share an implementation
Show how a principle or pattern looks in a real stack. Code, trade-offs, and what you would do differently are all useful.
Contribute research
Results from testing products with agents: where they guessed, what broke, what helped, and how you measured it.
Challenge the framework
If a pillar, principle, or term is wrong or missing, propose a change with the reasoning and evidence behind it.
Proposed contribution lifecycle
A proposal for how contributions will move through review.
- 01
Draft
Anyone writes a proposal using the pattern or principle structure.
- 02
Discussion
Open review focused on evidence, clarity, and overlap with existing content.
- 03
Accepted as draft
Merged into the framework, labelled as a proposal.
- 04
Revised
Updated as implementations and research accumulate.
The public repository is not open yet
Contributions will be accepted through a public repository once it is published. In the meantime, the pattern and principle pages show the structure proposals should follow.