Platform rule
Platform first
The public site should explain Solar Vega itself: what it is, how hosted agents work, and how a client enters their own workspace.
Solar Vega
Hosted agent workspaces
Public platform entry. Separate internal studio.
Solar Vega is the platform front door. Visitors should understand what the application does, how hosted agents work, and where new or existing clients go next. Named demo businesses still exist for testing, but they now sit behind explicit customer-view and client-login links instead of posing as the permanent public message.
Access map
Public intro
/Platform explanation, product framing, and the first call to action.
New client onboarding
/client/onboardingStart shaping the tenant's agent, tone, and workflow without showing a named demo tenant.
Existing client access
/clientBusiness selector for client/operator portals. Each tenant then continues through its own PIN-gated preview route.
Business/customer view
/svl/:tenantCustomer-facing direct links that open the agent conversation page for a specific business.
Internal studio
/officeOperator-only path. Stays behind the studio gate on the dev host.
Platform rule
The public site should explain Solar Vega itself: what it is, how hosted agents work, and how a client enters their own workspace.
Platform rule
New clients go to the wizard. Existing clients use the access portal. Internal staff stay on a separate studio route.
Platform rule
Phone and tablet stay touch-first. Desktop expands into the tenant office habitat without exposing the internal operator shell.
How it works
The public site explains the application first. Tenant branding and specific service tone come later, once someone is inside a chosen onboarding or client route.
Step 01
The public landing page introduces Solar Vega as an agent-hosting platform, not as a tenant gallery.
Step 02
New clients begin onboarding. Existing clients open the access portal. Internal staff use the protected studio route.
Step 03
The wizard collects the business tone, brand cues, and working style that define the client's front-facing companion.
Step 04
Phone and tablet stay swipe-led first. Desktop grows into the client office once the same session needs more space.
Temporary development portals
These portals stay available for QA and review, but they should remain secondary to the public platform story and the generic client-entry flow.
ExpandProperty operations
Temporary development portal only. Use it for preview and testing, not as the permanent public tenant directory.
Route split
/svl/virtual-property-manager
/client/virtual-property-manager
/client/virtual-property-manager/onboarding
/client/virtual-property-manager/home
Demo cues
Beauty studio
Temporary development portal only. Use it for preview and testing, not as the permanent public tenant directory.
Route split
/svl/lash-sensations
/client/lash-sensations
/client/lash-sensations/onboarding
/client/lash-sensations/home
Demo cues
Refill operations
Temporary development portal only. Use it for preview and testing, not as the permanent public tenant directory.
Route split
/svl/vega-refill
/client/vega-refill
/client/vega-refill/onboarding
/client/vega-refill/home
Demo cues
Project services
Temporary development portal only. Use it for preview and testing, not as the permanent public tenant directory.
Route split
/svl/vega-projects
/client/vega-projects
/client/vega-projects/onboarding
/client/vega-projects/home
Demo cues