RFC: Platform architecture — looking for feedback before we build

[achalagrawal]

k4m2a-architecture.pdf

I'm trying to work through designing the architecture for how K4M2A could be structured to serve multiple communities (K4M2A, Madhyasth Darshan, and eventually other communities like Vedanta, Osho, Dada Bhagwan etc.) from one codebase. Document attached.

This is genuinely a request for comments, not a finished plan. I've made some opinionated calls and I want to know where they're wrong before we start building. Especially with AWS and CI/CD setup.

The shape of the proposal:

• One shared PDS at maanav.net for all communities — leaning into how AT Protocol is meant to work
• One codebase, N brands via configuration rather than forking per community
• AWS for everything: ECS Fargate (web), EC2 (PDS), ALB (multi-brand routing), with PR previews on Fargate Spot

The document goes deeper into GitHub org structure, branch strategy, CI/CD, the multi-brand routing setup, and a proposed setup order for actually building this.

Things I'd love feedback on:

• Does the config-driven branding approach actually hold up, or are there cases where a community will want enough divergence that a fork is unavoidable?
• Is maanav.net the right home for the shared PDS?
• AWS Fargate vs. alternatives — anyone with strong opinions on running Go services in production? Should we use the Go service for OG metadata or some other way to it?

Also genuinely interested if anyone thinks the whole multi-tenant premise is wrong and each community should just run their own fork.

Reply here, or open a separate discussion for any thread that deserves its own space.