AUP

WordPress and Astro both ask a site to declare its content model. That is not a flaw; it is a different trade-off. ARC's Web Device tries to make common web work a runtime, while leaving the meanings of products, terms, and events to object data and application components. This is about where that boundary belongs, and what still has to be supplied to make it hold.

Web Device is one of ARC's core capabilities: declare a .web/ folder anywhere in AFS, and the data and AUP under it get rendered server-side into a website, SEO checks, broken-link detection, and visitor analytics included for free. This piece covers how it differs from UI Device (/dev/ui/web), how to use it, and which situations call for which.

ArcBlock founder and CEO Robert Mao will give a keynote at the 1st Harness4GenUI workshop, held during ASE 2026 in Munich, Germany.

The runtime for Blocklets. It gives a developer a place to run an application described as a Blocklet, together with the resources that Blocklet declares it needs.

AFS (Agentic File System) turns the files, services, and active work relevant to a task into an inspectable resource view. Instead of handing an agent an undifferentiated machine or a pile of APIs, it gives the task a world with names and boundaries.

ARC is the runtime for Blocklets. It gives a developer a place to run an application described as a Blocklet, instead of making the runtime, the application, and its resource connections one unexplained deployment.

Useful context is more than a prompt. It includes the documents, tools, and permitted actions that are relevant to the task. If those boundaries are vague, a capable model still has to guess what it may use.

Treats the browser as a device you can operate live, rendering AUP right there in the browser.

Declare a .web/ folder anywhere in AFS, and the data and AUP under it get rendered server-side into a website.