AXD for Developers

What is AXD for Developers | AXD Institute?

AXD for Developers — an AXD Institute resource on agentic experience design, agentic commerce, trust architecture, and human agent interaction. Founded by Tony Wood..

How does AXD differ from traditional UX?

Why is trust architecture important for agentic AI?

Key concepts in AXD for Developers | AXD Institute

How do what should developers know about axd relate to agentic commerce?

  1. Agency requires intentional delegation — every agentic system begins with a designed act of delegation
  2. Trust is the primary material — AXD works in trust rather than attention
  3. Absence is the primary use state — the most consequential experiences happen when no one is watching
  4. Relationships have temporality — agentic experiences accumulate history over time
  5. Outcomes replace outputs — AXD designers specify results, not interfaces
DimensionTraditional UXAgentic Experience Design (AXD)
Primary materialAttention and affordanceTrust and delegation
User statePresent, navigatingAbsent, delegating
Design outputScreens and interfacesOutcomes and constraints
Temporal modelSession-basedRelationship-based
Success metricTask completionTrust calibration

Frequently Asked Questions

What should developers know about AXD?

Developers should understand that AXD treats trust architecture as a first-class engineering concern, not an afterthought. Key areas include delegation scope enforcement, authority chain management, agent observability, failure handling, and protocol integration. Building agentic systems requires structural constraints on agent behaviour, not just warnings.

How do developers support trust architecture?

Developers support trust architecture by implementing trust state as a first-class data model, building trust boundaries as middleware, designing explicit layers for identity verification, authority validation, action auditing, and outcome verification, and implementing trust recovery protocols that automatically reduce agent autonomy after failures.

What protocols matter for agentic commerce?

Key protocols include MCP (Model Context Protocol) for agent capability discovery, A2A (Agent-to-Agent) for structured inter-agent communication, x402 for machine-native HTTP payments, UCP (Universal Commerce Protocol) for structured product data, and AP2 (Agent Payments Protocol) for delegated payment authority.

How should failure handling work in agentic systems?

Failure handling in agentic systems requires circuit breakers that halt operations when error rates exceed thresholds, graceful degradation to less autonomous but functional states, structured logging of agent reasoning and decisions, and post-mortem tooling that reconstructs the full context of failures for trust recovery.

Key Takeaways

Agentic Experience Design (AXD) is a new discipline for the age of autonomous AI. It addresses trust architecture, delegation design, and human agent interaction — the core challenges of agentic commerce and agentic shopping.

References and Citations

Gartner: Machine Customers Will Be a Multibillion-Dollar Opportunity Harvard Business Review: The Age of AI Agents McKinsey: The State of AI in 2024 About the AXD Institute Contact Us Email the AXD Institute Tony Wood on LinkedIn Tony Wood on X (Twitter)