Deployment form
A believable service-deployment flow spread across three screens: service details, runtime choices, and a final review before an asynchronous deploy.
The application owns its values and layout while Form coordinates the behavior that should be consistent: validation, first-invalid focus, server errors, and duplicate-safe submission. Each screen is an ordinary route, so going back preserves the draft without a form schema or wizard abstraction.
Try it: continue with an empty name to see first-invalid focus, then use the reserved name fleury to trigger a server error. Complete the flow and go back once to see the app-owned draft survive navigation.