Build a first AUP app

This path uses minimal-app because the current CLI explicitly provides it and can explain its sources, generated artifacts, and checks. It creates a complete slice rather than pretending to be a pure-AUP app.

Inspect the recipe boundary first

arc blocklet recipe explain minimal-app

On 2.0.0-beta.25, the output identifies web, aup, agent, and settings capabilities, and lists source DSL, AFS data, compatible artifacts, and the profile check.

Create the app

arc blocklet create ./hello-aup --recipe minimal-app --name hello-aup

In this page's verification, the CLI confirmed 18 created files and printed a next validation command using the resolved absolute path of the created directory. That absolute path depends on where you create the project, so do not treat it as tutorial syntax.

Created minimal app blocklet "hello-aup" with 18 file(s).

After creation, read these sources instead of editing generated artifacts:

The recipe also writes some JSON compatibility artifacts, but it does not materialize .aup/app.json, .aup/pages/*.json, or .aup/wrapper.json in advance. If a consumer explicitly needs them, read Generate, lint, and migrate; do not hand-edit them when no consumer needs them.

Continue to Validate, run, and inspect.