Build a managed globe platform for ambassador programs, with auth, profiles, and analytics, monetized via subscription.

You are building a fresh implementation inspired by the crafter-station/codex-globe repository.
Treat the repository as a reverse-engineering reference, not as the default destination codebase.
Infer the product, architecture, entities, and flows from the reference repository, then rebuild the core system intentionally from scratch.
Do not blindly clone the original repo. Do not default to patching or refactoring it in place.
Build in small phases and keep the first version focused and maintainable.
Product thesis: Provide organizations with a managed, customizable, and interactive globe to showcase their global ambassadors, partners, or chapters.
Commercial/product framing: Organizations with geographically distributed ambassador programs need a frictionless way to visualize and manage their network. A hosted, no-code globe with integrated profiles and analytics beats DIY WebGL.
Target user: Community managers and event organizers at technology companies with ambassador programs.
MVP scope:
- Interactive 3D globe displaying ambassador locations with auto-rotation and pause-on-hover.
- Ambassador profile cards on click (name, country, bio, social links, avatar).
- Continent and country filters with a toggle to grid view grouped by geography.
- Authentication for admins via email/password or GitHub OAuth.
- Admin panel to add, edit, or remove ambassadors (name, location, photo, links).
- Static events page showing upcoming events with a separate events globe.
- Custom subdomain for each organization (e.g., org.codexglobe.com).
- Vercel Analytics integration to track page views and interactions.
Stack assumptions:
- Next.js 16 (App Router) with React 19 and TypeScript as the full‑stack framework.
- cobe v2 for WebGL globe rendering, driven by latitude/longitude data stored in DB.
- Tailwind CSS v4 and shadcn/ui for styling, with flag-icons for country flags.
- PostgreSQL database hosted on Vercel Postgres or Neon, connected via Prisma ORM.
- NextAuth.js for authentication, supporting GitHub OAuth and credentials.
- Stripe integration for subscription billing, with metered pricing per ambassador.
- Vercel for deployment, analytics, and edge functions.
Key entities:
- Ambassador: id, name, latitude, longitude, country
- Organization: id, name, slug, subscription_tier, ambassador_count
- Event: id, title, description, date, latitude
Core pages / routes / flows:
- Public Globe Dashboard (/[orgSlug]): Main interactive globe page showing ambassadors of a specific organization.
- Events Globe (/[orgSlug]/events): Separate globe view filtering events with list/grid toggle.
- Admin Login & Dashboard (/admin): Auth gate; redirects to ambassador CRUD interface after login.
- Ambassador Management (/admin/ambassadors): Table listing ambassadors with add/edit/delete actions using shadcn/ui forms.
- Landing Page (/): Marketing page for the hosted platform, pricing, and sign‑up.
Backend services / modules:
- Ambassador Service: CRUD operations for ambassadors, geocoding lookup or manual lat/lng entry, validation.
- Auth Service: NextAuth‑based authentication, organization‑scoped access, session management.
- Subscription Service: Stripe integration, metered billing per ambassador, plan management webhooks.
- Analytics Service: Capture page views, click events on ambassadors, and funnel data for customer reporting.
Do not build yet:
- Custom 3D rendering engine (rely on cobe; only extend if library is insufficient).
- Native mobile apps (mobile‑web responsive is sufficient for MVP).
- Advanced analytics dashboards with complex aggregates (start with Vercel Analytics).
- Community features like forums, comments, or messaging within ambassador profiles.
- Integration with CRM or HR systems (YAGNI until enterprise demand is proven).
- AI‑powered ambassador matching or recommendation engine.
- Multi‑language i18n support (defer until international customer base exists).
Major risks / blockers:
- Market size unvalidated; Codex may be the only organization needing such a tool.
- Performance issues with cobe on low‑end devices or with many markers (scalability unknown).
- Dependency risk: cobe is a single‑developer library; API changes or abandonment could break the product.
- Monetization friction: community managers may have no budget for a visualization tool.
- Team bandwidth: a single developer can’t simultaneously build, market, and support with reliability.
- Multi‑tenant data isolation must be perfect from day one; a privacy leak could be catastrophic.
Work in phases. After each phase, summarize what was built, what remains, and which assumptions from the reference repo you intentionally did or did not keep.

Phase 2 core flow

Objective: Add PostgreSQL, Prisma, and multi‑tenant auth for organizations.

Deliverables:
- Database schema for Organization, Ambassador, and Event (Prisma migration).
- NextAuth with GitHub OAuth and credentials provider.
- Admin middleware to protect /admin routes.
- Seed script for demo organizations.
- Exit: Admin can log in and see an empty ambassador list; database is hosted on Vercel.

Rules:
- Implement the core pages, routes, and backend modules needed for the happy path in the fresh build.
- Use the reference repo for behavior and architecture cues, not as the code target.
- Preserve maintainability and add only the minimum comments needed.

Start by reverse engineering the reference repository, then implement the fresh build in the smallest clean sequence.

Deploy and finalization

Objective: Prepare the implementation for release, verification, and handoff.

Deliverables:
- Verify the main flows work.
- Check configuration, environment assumptions, and release blockers.
- Summarize remaining risks and suggested follow-up work.

Rules:
- Do not add speculative infrastructure.
- Focus on practical release readiness, tests, and explicit known gaps versus the reference repo.

Start by reverse engineering the reference repository, then implement the fresh build in the smallest clean sequence.