Contact screens keep labels, consent, and safe error messaging visible so the public experience stays polished under load or denial paths.
This screen points to the documented Website form API and keeps the submission states visible inside the page shell.
Commercial, support, and partnership intent remain explicit in the public form path.
Consent, validation, and safe error handling remain visible in the same shell.
Operator routing happens privately while the public page keeps a clean retry path.
The foundation shell makes non-happy paths visible at the screen level so later runtime wiring does not hide denial, retry, loading, or release dependencies.
Contact messages move through the same queue, consent, and audit-safe workflow as demo requests.
Operator routing and acknowledgement templates can resolve after validation completes.
Labels and consent notes stay visible so disclosure and privacy expectations are explicit.
Invalid or abusive submissions fail without internal failure details or policy text.
Contact and newsletter workflows stay visible from one accessible route with safe failure handling.