Customer account

This first slice is intentionally read-only and is scoped to the signed-in customer's own products, subscription status, renewal dates, and licence details.

Checkout policy for the future purchase flow is already fixed: guest purchase is not allowed. Customers will need to sign up or sign in before completing a purchase so orders, subscriptions, and licence ownership stay attached to a verified account.

Sign-in and private subscription data are not enabled here yet because this site does not currently have verified customer-auth/session ownership wiring or an authoritative subscription/licence data source connected.

Planned read-only fields

Products: unavailable until a verified customer→subscription source is connected
Subscription status: unavailable until status semantics are defined by the source system
Renewal dates: unknown until verified timezone/date rules and real records exist
Licence details: unavailable until approved customer-visible fields are defined

Purchase-flow policy already decided

Anonymous browsing and anonymous cart building can remain available
Checkout must require sign up or sign in before order creation
The canonical anonymous cart must survive the auth return and then be associated on the server with the verified customer account
Orders, subscriptions, and licences must be owned by that verified account, not by browser-only state

Verified blockers right now

No confirmed Intranetrix customer sign-in route or callback is configured in this site
No verified signed-in subject → customer/account ownership mapping is implemented
No authoritative subscription, entitlement, renewal, or licence read API is available for this website
No private customer data should be embedded in static HTML, generated pages, or public caches

Intended architecture once those blockers are cleared

The backend renders the account page shell and owns customer scoping
The browser rehydrates only the signed-in customer's private account data after verified authentication
Checkout preserves the anonymous canonical cart through auth return, then the server performs verified account association before checkout/order creation
Unknown or unavailable fields stay explicitly labelled as unknown or unavailable
Missing renewal data must not be treated as perpetual access or a successful empty state