UI · Intermediate · runnable fixture source
Capture now, complete when ready
Use form contracts to accept a minimal intake while keeping missing readiness fields visible.
@lssm-tech/example.form-showcase · Test and preview source inspected · evidence as of 2026-10-27
Source context
Test and preview source inspected · b67c376f
Pinned source links require repository access; publication and anonymous package availability were not checked for this example.
A customer intake can begin with a name. In the fixture, a quick capture is accepted while email, phone, and consent remain completion debt. A richer profile can then determine whether the record is ready for the next workflow.
What you will learn
- Describe form controls and layout with FormSpec metadata.
- Separate accepted intake from a complete business record.
- Expose public form and proof entrypoints without depending on private preview helpers.
AN INTERACTIVE READING MAP
Walk through this example.
Step through the maintained source review, inspect its evidence boundaries, or assemble an adaptation packet.
SOURCE WALKTHROUGH
Read the operation in its authored order
01 / IN FOCUS
Choose the form contract
Inspect all-fields, progressive-steps, and customer-projection forms. The package includes field kinds, conditional rules, sections, and step layouts.
1 / 4
0 points in your packet
Walk through the source
- Choose the form contract. Inspect all-fields, progressive-steps, and customer-projection forms. The package includes field kinds, conditional rules, sections, and step layouts.
- Inspect minimal intake. The quick-capture fixture contains a customer ID and display name. The smoke test expects capture to succeed and completion to remain incomplete with email, phone, and consent debt.
- Inspect conditional validation. Another test builds Zod validation with relations and expects a missing repeated contact value to be reported at contacts[0].value.
- Use the public proof map. The proof-config export lists docs, sandbox, forms, and UI entrypoints. Adapt through the supported exports, then supply your own persistence and submission behavior.
What this review establishes
- The inspected fixture separates acceptance from completion status.
- The source tests inspect field coverage, step layout, conditional validation, and public exports.
- The public preview is deterministic fixture state with no required backend or credentials.
Not established
- Production form storage, submission delivery, or authentication.
- A production renderer for every host application.
- A PII hint automatically implementing a privacy control.
Before adapting
- Access to the inspected source repository and a checkout at the cited revision.
- The repository's Bun workspace dependencies and required generated package exports. These instructions were inspected; the examples were not executed in this review.
Adapt the pattern
- Decide which fields block intake and which block later readiness.
- Map the FormSpec fields to your host design system.
- Add storage, submission, and authorization tests when connecting the form to real actions.
- declaredStability
- stable
- registry
- Registered
- inlinePreview
- Registered
- execution
- Not rerun
- production
- Not assessed