Skip to main content

Current source example; target acceptance still required

Example: local state and events

Read the current DSL Showcase `set-sugar` source as a source-level state/event example, not a deployed behavior guarantee.

The current DSL Showcase registers a set-sugar page. Its source contains a compact authoring example:

aup
button rename "Rename" primary ->
  set headline props {content: "Renamed"}

button load "Load" primary ->
  set list src "/modules/index"

The first action targets a named node’s props; the second changes a named node’s data source. Both compile into the AUP node/event contract described elsewhere in this board.

What this example proves

  • The current DSL parser/compiler accepts these two set shorthand forms in Showcase source.
  • The named target makes the intended local update inspectable in source.
  • The file is registered in the current DSL Showcase app page map.

What it does not prove

  • A remote deployment or any historical static Showcase page is live.
  • /modules/index is readable in every session, scope, or target.
  • Every renderer presents the same update or interaction.

To turn this into a product claim, run the registered app locally in the target runtime, trigger each action, and record the target, URL, version, and observable result. Do not cite the source file alone as an end-to-end acceptance result.

Read Events, state, and bindings for the contract and Caller identity and safety for the permission boundary.