Choose a layer from the problem to solve, not from a directory name or a Showcase first:
| Task | Read first | Do not assume |
|---|---|---|
| Describe an interface tree, event, or state | Core concepts in this board | Every node presents the same way on every device |
| Check actual device capability and shared degradation rules | Capability/renderer and core concepts | The renderer alone defines the capability contract |
| Write an app or page in maintainable source | The DSL section in this board | DSL is a separate runtime protocol |
| Build a static site, content page, or theme | The target's Web Device documentation | AUP itself defines a site’s directory or content model |
| Browse a visual example | The matching Showcase example | A physical source file is necessarily an accessible, deployed demo |
minimal-app is the first verified path, but it is not a recipe that creates only one AUP file. It creates one Web page, one AUP app, one agent, and settings-shell source/defaults. Its profile checks declared pages, capabilities, and structural limits; activation seeds the settings defaults into /instance, so the profile itself is not proof that all four capabilities have run end to end.
This draft uses AUP as the short name. Source material contains multiple long-form and historical terms; until product naming is settled, no extra protocol promise should be inferred from one older expansion.