Public routes stay in Next.js while manual HTML content remains outside the framework.
Platform Overview
`Next.js` owns the public, member, and admin surfaces while the client’s manual HTML pages stay untouched under `content/manual-html/` and continue loading the protected player through shared platform assets.
The platform now covers login, membership verification, protected playback tokens, operator workflows, and a simulated join flow that provisions member credentials end to end.
Client-managed pages do not need to move into the app. They continue using `data-video` placeholders plus the shared loader in `content/assets/`, while the API and worker handle the secure playback contract behind the scenes.
PasswordSentry-backed sign-in validates credentials first, then the API confirms local membership status and expiry.
Open surfaceThe public purchase surface stays app-owned, with the current phase using a simulated crypto payment to provision credentials.
Open surfaceMembers can confirm that the bearer token still maps to an active local access record before opening protected pages.
Open surfaceOperators can create access, rejoin expired members with fresh credentials, and manage expiry without turning this into a CMS.
Open surfaceThe API owns auth, playback, admin, and payment boundaries. The worker owns heavy FFmpeg jobs. Manual HTML stays client-editable and only depends on shared runtime assets.