Customer EntryOpen BrainCaps as a product, not as a concept.
Cette surface prend le relais apres PortalHQ. Elle n'ouvre pas de shell parallele: elle montre le workspace BrainCaps, ses signaux de sante et ses premiers parcours metier.
route overviewcustomer surfaceportal driven
Runtime modePending
La session PortalHQ partagee n'est pas visible ici. Utilise l'URL dev partagee plutot qu'un alias local si tu veux reemployer la session shell.
Resolved planUnknown
Le plan effectif apparaitra ici des que le bootstrap serveur pourra lire le contexte produit.
Tenant scopeUnresolved
Le tenant client reste a resoudre tant que le contexte PortalHQ final n'est pas complet.
Critical depsUnknown
Aucun signal runtime n'est encore remonte vers overview.
Bootstrap SnapshotWhat overview can already read from the product contract
Le bootstrap overview reste volontairement prudent tant que les variables de contexte serveur ne sont pas completes.
- Organization sourceAucune source d'organisation PortalHQ n'est encore visible pour cette surface.
- Team contextLe shell ne pousse pas encore un teamSlug resolu par defaut.
- Organization contextAucun organization id bootstrap n'est encore configure pour cette surface.
- Bootstrap noteLa session PortalHQ partagee n'est pas visible ici. Utilise l'URL dev partagee plutot qu'un alias local si tu veux reemployer la session shell.
- API basehttp://braincaps-api.braincaps.svc.cluster.local
- Auth modeAucun mode d'auth runtime n'est encore disponible.
- Launch targetLes deep-links seront consideres stabilises quand la surface cliente sera resolue en environnement.
- Health rowsAucun signal de sante n'est encore remonte par le bootstrap overview.
MVP RouteWhat overview must clarify immediately
The overview route is the product landing zone once PortalHQ opens BrainCaps.
- Workspace statusShow whether BrainCaps is active, provisioned, suspended, or waiting on setup.
- Tenant contextMake the resolved tenant and workspace scope visible to the customer.
- Health snapshotSurface the first runtime cues the customer can act on without reading infra logs.
Current API FitData that already exists on the backend
The current backend already exposes useful product signals for a first overview.
- Plan widgetResolved plan and activation state from PortalHQ are already exposed.
- Quota widgetUsage and limits can be read before a richer custom dashboard exists.
- Health widgetRuntime readiness and dependency health can be shown without inventing a new contract first.
Boundary RulesWhat must stay outside this app
These capabilities remain shell or operator concerns, not customer surface concerns.
- Auth and account managementHandled by PortalHQ and never duplicated here.
- Billing shell and customer portalRouted back to PortalHQ rather than rebuilt locally.
- Operator administrationHandled in braincaps360 with private access only.