Vendor application page

Route and purpose

Route: /submit

This page submits a new application or presents the existing application's receipt and status. Dynamic segments in square brackets are replaced with the requested resource's slug or identifier.

Access and identity

• Intended audience: Customer, Vendor.
• The page shell can redirect or gate the interface, and every backing API independently enforces authentication, role, status, and ownership.
• A copied URL never grants access to a protected resource.

Page behavior

1. Resolve the route and any dynamic parameter.
2. Load public data or establish the authenticated application session.
3. Render an explicit loading, empty, success, or error state.
4. Submit mutations only through the page's protected action.
5. Refresh the relevant server state after a successful change.