Form system
A3S UI's structured-form components keep schemas, visual design, controlled rendering, and validation on one deterministic contract. They use the same A3S UI visual language as buttons, fields, data grids, and application shells. Examples live directly in the component guides; there is no separate product site or form demo route.
Choose an integration layer
React applications install react, react-dom, and react-hook-form when needed. Vue applications install vue. Both framework surfaces share one Form Core instead of producing a second schema or validation contract.
Current component capabilities
- 23 built-in fields plus matrix, repeater, data-grid, file-upload, and signature extensions;
- grid, column, card, tab, collapsible-content, and branched-wizard layouts;
- deterministic computed rules, host-owned async validation, dynamic data sources, and locale catalogs;
- A3S Form Schema Profile 1 and native Rust/WASM submitted-value evaluation;
- controlled React, Vue, and Web Component adapters with shared read-only, error, locale, and host-capability boundaries.
Start here
React and Vue hooks explains how both framework-state surfaces share Form Core.
Use Built-in fields for scalar controls, Layouts for composition, Repeatable field groups and Data grids for arrays, and Wizards for multi-step flows. Run the migration checklist before publishing a new revision or digest.
Product boundary
The components own document compilation, controlled values, interaction, and inspectable change. Persistence, identity, permission, credentials, file storage, network requests, business side effects, and final submission remain host-owned.
