#Playground

The Playground uses the same A3S UI workspace and editor contracts as other A3S Office surfaces. Its default interface is Chinese.

#Browser-local workspace

The home screen lists every form stored in the current browser. It supports:

• searching by title or description;
• viewing field count, revision, and last update time;
• creating a blank form or starting from the onboarding template;
• importing a JSON document after deterministic compile validation;
• moving between the form list and Designer; and
• restoring the workspace after a reload.

Workspace data uses the versioned a3s-form-workspace:v1 key in localStorage. Legacy single-form data is migrated on first read. Corrupt or unavailable storage falls back safely to the current session.

#Designer workspace

Desktop authoring combines the component catalog or structure tree, the canvas, and the property, validation, or Agent inspector. Compact screens expose the same tools as dedicated Components, Canvas, and Settings panels so each task gets the full available width.

Preview is intentionally focused: it removes both authoring sidebars and renders the real controlled runtime on the canvas. The toolbar reports saving, saved, and failed states, and Cmd/Ctrl+S follows the same save path as the visible Save action.

#Agent FormPatch

The Agent inspector accepts revision-bound FormPatch JSON rather than free-form model output. It shows the current revision and protocol, provides an empty patch template, preflights JSON syntax, and reports revision conflicts before any document mutation.

#Runtime validation

Submit actions validate the form, render a clickable error summary, and focus the first invalid field. Errors update as values are corrected. Draft actions dispatch the current controlled value without being blocked by required fields, while asynchronous actions expose progress, prevent duplicate activation, and report failures.