You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
Learning path
From protocol to site
Understand an interface tree, its protocol and how a website presents it.
For readers familiar with AFS-UI who want to understand its implementation layers. You do not need to memorize every type first.
Start with AUP, nodes, data connections and events. Then examine Web Device’s site responsibilities and compare primitives with theme components.
You should finish able to explain why a core primitive is not a Web theme component, and why a successful site build does not validate every device interaction.
Along this path
- What is AUP?
Agentic UI Protocol describes interface structure and its connections to state and actions.
- What is in an AUP tree?
Read identities, types, properties and children through one task card.
- How do src, bind and propBind differ?
Reading resources, writing input and updating properties are distinct connections.
- What happens after a click?
Trace an interface event to an explicit operation target.
- What is Web Device?
Organizing content and interfaces into a website is another layer of work.
- How do AUP and Web Device divide responsibilities?
One describes interface contracts; the other organizes a Web site implementation.
- Which primitives does AUP define?
Eighteen core types provide an entry into the interface vocabulary.
- What are Web Device components?
Distinguish core primitives, Web-only types and theme components, then browse the default theme.
- Can every device render the same interface?
Capability declarations and degradation determine how a structure reaches its target.
Check your understanding
What distinctions should you be able to explain afterward?
Protocol expression, device implementation, site organization and theme component responsibilities.