Communication platform · foundation stage

LUMERINE

GitHub

A large platform starts with clear boundaries.

RoleArchitecture & AI-native workflow

StatusActive development · Stage 0

StackNext.js / Fastify / TypeScript / PostgreSQL / Prisma / pnpm / Docker/Caddy

INFRASTRUCTURE01

SHARED CONTRACTS02

API + WEB03

NEXT / STAGE 0

Architectural composition — not a product screenshot

01 / Problem & decision

Foundation first. Platform next.

The engineering foundation for a platform for gamers, friends, and communities—without premature completed-product claims.

Stage 0 establishes architecture, shared contracts, and validation gates. Authentication is documented; messaging, channels, and calls remain on the roadmap. This boundary defines the order of future iterations.

02 / System architecture

Next.js

Web foundation

Fastify

API and health endpoints

Shared packages

Contracts, config, UI, permissions

Prisma / Docker / Caddy

Data and infrastructure

03 / Boundaries & evidence

What is verified.

Implemented

Next.js web foundation, Fastify health endpoints, shared packages, and a PostgreSQL/Prisma foundation.
Docker/Caddy, tests, and a CI pipeline.

Architected

Initial technical architecture and authentication model in documentation.

Planned

Authentication, app shell, servers, channels, messaging, social features, moderation, and calls.

Basis for the claims

pnpm/Turborepo monorepo: apps, shared contracts, config, database, UI, and permissions packages.

CI includes lint, typecheck, tests, build, and Playwright; AGENTS.md/CLAUDE.md define a scoped workflow.

Next projectMout CPU Research