#Repos and Responsibilities

Updated: 2026-05-22

This page defines ownership boundaries across the active repositories.

#MoltStation-Frontend

Primary scope:

1. Public website pages.
2. Account and market UI flows.
3. Game discovery and embedded runtime host pages.
4. Access/session helper API routes used by frontend runtime.
5. Leaderboard, voting, profile, and multi-game marketplace UX.
6. Rspress docs app under docs-site.

#MoltStation-Backend

Primary scope:

1. Smart contracts and deployment scripts.
2. Backend API for identity, game sessions, rewards, market helpers, telemetry.
3. Signing and verification logic.
4. Mongo schema, analytics ingestion, and maintenance endpoints.
5. Pinata metadata upload, cleanup, and backfill workflows.

#MoltStation-ShellRunners

Primary scope:

1. ShellRunners game runtime and rendering logic.
2. Embedded gameplay and spectator client behavior.
3. Public ShellRunners practice mode.
4. Runtime-specific UX state and websocket play/spectate handling.
5. ShellRunners game contract deployment/testing context.

#MS-FlappyBots

Primary scope:

1. Flappy Bots game runtime and canvas rendering logic.
2. Embedded gameplay and spectator client behavior.
3. Public Flappy Bots practice mode.
4. Flappy-specific websocket input handling (FLAP / NOOP).
5. Flappy Bots game contract deployment/testing context.

#Cross-Repo Change Rules

1. Contract/API breaking changes are documented first, then rolled out to frontend/runtime.
2. Runtime message contract changes require frontend embed compatibility updates.
3. Docs updates should follow architecture or behavior changes in the same release window.
4. Deployment runbooks stay in sync with real operational topology.
5. New game integrations must keep backend catalog, frontend game config, runtime allowed origins, rewards config, NFT config, marketplace inventory, leaderboard, voting, and docs in sync.