Soul Chat MVP
Sign in first. Then configure your model. Then enter the social workspace.
This is a progressive product flow, not a one-page control panel. The first screen should only help you create identity, unlock local model settings, and move into the real product in the right order.
Client-side soul generation
Thin Cloudflare persistence
OpenAI-compatible providers
Register or login
RequiredSet AI model
Mock modeContinue to product
LockedStep 1
Register or login before anything else
If you are not signed in, this product should not dump you into soul editing, session records, friend review, or settings. The only job here is getting identity ready and then unlocking step 2.
Anonymous sign-in now. Email, phone, or OAuth upgrade later.
Keep provider URL, token, and model local to this browser.
Soul first, then sessions, friends, and settings.
Soul management
Session management
Friend review
Personal settings
Step 1 required
Access gate
Register or login
Create a lightweight anonymous identity first. After sign-in, local model setup unlocks and Soul becomes the first destination.
You tried to open a protected page. Sign in first, then start from Soul.
Auth status: signed out. Create an anonymous session to sync backend data.
Sign-in unlocks local model setup and the workspace order starts from Soul.
Step 2
Fill AI model config
Sign in first to unlock local model settings. These never move into the backend worker.
BigModel is the default preset. Any OpenAI-compatible base URL, token, and model can replace it.
After login
What opens in order
Soul management
Generate, review, evolve, and back up the client-side soul.md.
Session management
Create bounded chat rooms, save important turns, and summarize trials.
Friend review
Inspect nearby preference and explainable compatibility snapshots.
Personal settings
Update identity fields and upgrade the login method after the core flow.
Product rule
Why the order matters
- Unauthenticated users should not see the real workspace as if they are already inside.
soul.mdgeneration and model traffic stay on-device, so backend auth is only about persistence.- Settings belong at the end because they support the social loop; they are not the primary entry point.