PortalHQ
braincaps-app explains usage; it does not replace the billing shell.
Make plan, quotas, and consumption legible to the client.
La route usage ne refait pas le billing shell PortalHQ. Elle montre ce que BrainCaps comprend du plan actif, des entitlements et des limites metier appliquees cote produit.
Entitlements
Limits should be resolved from the PortalHQ context and BrainCaps product logic.
No ambiguity
Usage, plan, and limits must be understandable without support escalation.
What usage needs to answer fast
A customer should understand what is enabled and what is constrained without reading raw entitlements.
- Plan identitySurface the effective plan code and activation context clearly.
- Quota consumptionShow current usage versus the quota BrainCaps is applying.
- Commercial next stepWhen a limit matters, route the customer to the right PortalHQ action, not a dead end.
What already exists today
The current product already exposes enough for a first usage page without inventing new billing logic.
- Dashboard quota widgetA first table of limits and usage is already present.
- Ops metricsCurrent ingestion and request counters are already available.
- Portal context parsingPlan and quota rows can be derived from the existing context helpers.
What not to confuse
This route explains product usage. It does not replace shell billing or customer-portal actions.
- Usage explanationBelongs in braincaps-app.
- Subscription managementBelongs in PortalHQ.
- Manual overridesBelong in operator workflows and must remain traceable.