Separated responsibilities
Public web, the auth/API control plane, the internal shell, sitemaps, and infrastructure evolve in one code home with explicit boundaries.
Platform architecture
One Brain Club platform with clean boundaries.
The new architecture keeps public web, workspace shell, sitemaps, and infrastructure in one home without forcing them into one deployable unit.
Four core build lanes
- public-web with an independent public-facing deploy
- workspace-shell as the next authenticated Brain Club layer
- backend-core as the Brain Club-native auth and API control plane
- sitemap-service as a separate heavy-SEO runtime
- infra-console as a Brain Club-native control surface
Monorepo, but not one deploy.
Iframe apps stay outside
Venture apps stay as separate repos and separate deploys while Brain Club owns the shell, bridge, and standards.
CCS as a temporary adapter
Migration starts with contracts and adapters, not a rushed lift-and-shift of the whole infrastructure.