A four-step flow that moves from private proof to public momentum.
Vault, Upload, Verify, and Activate are now their own full-page guide so the product story feels like a real system instead of a stack of disconnected claims.
Flow principle
Public pages introduce the system. Protected routes handle Private Vault and AI Scrutiny where trust actually matters.
Public shell for explanation and conversion.
Protected dashboard for stored work and AI analysis.
Automation only after verified readiness.
01
Vault
A protected private vault keeps raw links, work samples, and internal AI scrutiny inside authenticated routes.
The vault is where MeliusAI stores portfolio signal after sign-in.
This is intentionally separated from the public introduction pages.
Private Vault logic stays inside dashboard workflows, not the marketing shell.
02
Upload
Users drop GitHub repositories, Behance links, Google Drive folders, or portfolio sites into one universal intake.
Profession routing changes how the same input is interpreted.
Developers, designers, marketers, and HR users all enter through the same polished surface.
The goal is proof-first onboarding, not resume-first onboarding.
03
Verify
MeliusAI translates work into a score, goods vs. bads, a roadmap, and company-specific readiness gaps.
Verification focuses on explainable signal instead of vague hype.
The Ready Meter shows exactly what still blocks a target role.
AI Scrutiny remains in the protected dashboard layer where sensitive analysis belongs.
04
Activate
Once readiness crosses the threshold, the Melius Agent can move a verified portfolio into recruiter hands automatically.
Automation is gated behind a 90+ signal, not offered by default.
That keeps the experience ambitious without feeling irresponsible.
Users always understand why they are ready or why they are not yet ready.