A3S Form
  • next

      • Product roadmap

      A3S Form is moving from a sound contract foundation toward production form infrastructure for people, agents, A3S Cloud, and A3S Workflow. Work is ordered by semantic risk: runtime correctness comes before a larger component catalog, and lifecycle governance comes before SaaS-style expansion.

      Capability model

      LayerResponsibility
      Form CoreSchema profile, compiler, rules, validation, immutable plans, patches, revisions, and digests
      RuntimeField state, accessible rendering, layouts, data-source/action ports, localization, and incremental updates
      StudioVisual design, rule and integration configuration, preview, simulation, diagnostics, and change review
      GovernanceDrafts, releases, history, diff, rollback, approval hooks, audit events, and collaboration contracts
      Agent interfaceInspect, propose, patch, simulate, validate, test, and policy-bound publish requests
      Host platformIdentity, authorization, persistence, submissions, files, payments, webhooks, analytics, and secrets

      Milestones

      v0.2 — Runtime integrity

      • Lock in host-neutral embedding: controlled adapters, scoped CSS, package budgets, and a digest-pinned workflow-node configuration contract.
      • Define a closed A3S Form Schema Profile and reject unsupported keywords.
      • Stabilize deterministic computed rule evaluation and rule tracing for release.
      • Stabilize cancellable async validation and stable server-error mapping for release.
      • Stabilize data-source dependencies, triggers, caching, deduplication, search, pagination, and failure states.
      • Add field-level subscriptions, incremental rule evaluation, locale catalogs, and tracked large-form benchmarks.

      The current next baseline has completed the host-neutral embedding contract, CSS isolation gates, adapter parity, Schema Profile 1, deterministic computed-rule chains, cancellable host-owned async validation, host-owned data-source orchestration, field subscriptions, versioned runtime locale catalogs, and 100/500/1,000-node CI budgets. The remaining v0.2 work is compatibility review, final browser evidence, publication, and migration notes.

      v0.3 — Complex forms and complete Studio

      • Build on nested repeatable groups and editable data grids with deeper object authoring, matrices, dialog editing, bulk operations, and large-dataset interaction models.
      • Add true pages and wizards with branching, progress, page validation, review, and resume checkpoints.
      • Expand first-party fields and provide audited extensions for file, signature, address, rich text, and CAPTCHA use cases.
      • Add visual condition, calculation, validation, data-source, action, and payload editors.
      • Deliver reusable fragments, templates, theme tokens, RTL support, adapter parity, and a WCAG 2.2 AA baseline.

      The current v0.3 development slice is implemented but not released: object arrays compile to concrete row paths, repeatable groups can be nested, rows retain UI state through insert/move/remove operations without hidden metadata, and Designer authors the complete item schema. Computation, validation, visibility, enablement, and data-source dependencies can bind to nested rows. Object repeaters can now use layout: "data-grid" for a semantic desktop table and labeled row cards in narrow embedded containers; the Router Playground form uses that path for metadata-free routes, per-row validation, and host-owned branch options. Wizard layouts provide visible-rule branches, progress, page-scoped sync/host validation, final review, earlier-page error recovery, and digest-bound controlled checkpoints across React, Vue, Web Components, and Designer preview. Committed A3S Test flows cover wizard branching, page validation, review editing, grid add/edit/reorder/remove, row-bound options, semantic output, and desktop/390 px Chrome layouts. Matrix questions, dialog-based grid editing, bulk grid operations, Firefox/WebKit evidence, and the formal WCAG 2.2 AA audit remain open.

      v0.4 — Lifecycle and governance

      • Separate mutable drafts from immutable releases.
      • Add history, provenance, structured diff, restore, rollback, environment promotion, and approvals.
      • Add presence, locking, patch rebasing, conflict review, autosave, durable resume, and offline synchronization contracts.
      • Add audit, policy, PII, registry-version, signed-release, and migration contracts.

      v1.0 — AI-native production contract

      • Stabilize document, plan, patch, interaction, and release protocols with migration tooling.
      • Provide agent operations for inspect → propose → diff → simulate → validate → test → approve → publish.
      • Attach explanations, risk checks, fixtures, tests, provenance, policy results, reviewers, and release digests to agent-authored changes.
      • Ship reference lifecycle integrations for A3S Cloud and durable human-task integrations for A3S Workflow.

      Boundaries

      A3S Form documents will not execute arbitrary JavaScript. Form Core will not depend on A3S Cloud, A3S Workflow, Dify, or another platform runtime. It will not duplicate identity, secrets, submission storage, payments, analytics, or connector platforms. Those services stay behind explicit host capabilities.

      The canonical milestone scope, known v0.1 limitations, exit criteria, non-goals, and release gates are maintained in ROADMAP.md.