Extension setup
Thin browser client for TradeSea page reading, status, and the on-page panel.
Extension boundaryAngelTrade
Private alpha deployment
Passive trading behavior guardrails for the first real users.
AngelTrade is becoming a private-alpha web app plus Chrome extension for rule review, passive supervision, extension setup, and account-linked reports.
ModePassive supervision
Broker scopeTradeSea only
Alpha accessPrivate freeze
Live tradingBlocked by policy
Private engine
What-if simulation, optimization, and rule recommendation will run behind account auth.
Backend healthAccount sync
Extension installs will connect to a user account before receiving personal rules.
Auth nextAlpha workflow
The product areas are private, not gone.
The public site stays visible. The app workflow moves into protected Next.js routes while Supabase auth and private execution APIs are added in follow-up PRs.
Private app route
View statusInput Configuration
Upload trade files and create an analysis session.
Private app route
View statusWhat-If Simulator
Test rule packages against imported executions.
Account auth required
View statusLive Config
Review saved rule bundles before the extension receives personal rules.
Coming next
View statusExport My Data
Export reports and simulator runs after account storage exists.
Next.js shell
Private-alpha routes are online.
The extension bundle stays thin: DOM reading, TradeSea page status, connection handshake, and the on-page panel.
This route exists as a private-alpha shell. Upload and analysis persistence comes after auth and database PRs.
The simulator route exists as a private-alpha shell. Server-side execution moves behind authenticated APIs later.
Live rules will be loaded per signed-in user and fetched by the linked extension.
Exports need user-owned storage first, then a private dashboard action.
The next backend step is user identity, a database, and extension-to-account linking.