Skip to main content
Knowledge mapWhat is AUP?ArcBlock

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← AFS and interfaces

One question

What is AUP?

Agentic UI Protocol describes interface structure and its connections to state and actions.

  1. AFS contextConnect resources and operations
  2. AUP node structureInterpret and render
  3. Display
Relationship sketch · arrows show responsibilities and connections, not a complete protocol sequence.

Imagine a task card with a title, status and Complete button. AUP describes that interface as structured data.

A node has an identity (id) and a type (type). It can also carry properties, children, state and event bindings. A renderer turns this structure into an interface; supported bindings and events connect it to AFS resources and operations.

AFS supplies addressable context. AFS-UI is the architectural approach of building interfaces over that context. AUP gives the interface structure and interactions a concrete protocol expression. These are related layers, not interchangeable names.

For example, text expresses text and action expresses an action. That does not make every font, theme or website route a protocol concern.

Further reading

Technical documentation: read the full reference.

Check your understanding

How do AFS, AFS-UI and AUP relate?

AFS supplies operational context; AFS-UI relates interfaces to that context; AUP expresses interface nodes and interaction contracts.

Continue along a learning path

Referenced here

Terms

  • AFS UI

    AFS-UI builds interfaces over the addressable resources of AFS. People use a rendered interface; agents can inspect and operate its exposed structure through paths. AUP describes the interface and its interactions, while a UI device such as Web Device renders it.

  • AUP

    AUP (Agentic UI Protocol) lets an application express what is shown and what actions are available. A runtime then renders the parts that fit its device capabilities, instead of treating one screen's pixels as the application itself.