docs/ — Index¶
Map of everything under docs/, with freshness flags so agents and humans
know what to trust. Agent-facing guides live at the repo root
(CLAUDE.md, AGENTS.md) and in each major
directory’s CLAUDE.md.
This tree also builds as a Sphinx/MyST site for Read the Docs — conf.py,
requirements.txt and index.md (the landing page + nav) here, with
.readthedocs.yaml at the repo root. Build it locally with:
pip install -r docs/requirements.txt
python -m sphinx -b html docs docs/_build/html
New Markdown files are picked up by the globbed toctrees in index.md
automatically; a file needs an # H1 to get a nav entry.
The site is published in the same 16 languages as the product — see
translations.md for the pipeline, the translated-page
subset, and the Read the Docs per-language project setup.
Trust order for conflicts: code > docker-compose.yml/deploy.sh >
root CLAUDE.md / directory CLAUDE.mds > the reference docs below > dated
design docs/plans (historical snapshots — they describe intent at the time of
writing, not necessarily the current code).
Reference docs (keep current)¶
Doc |
Contents |
|---|---|
What the site consists of — hand-written area guides (social, economy, content, games/apps) plus generated inventories of every page route, API route, game and app ( |
|
Canonical code-layout overview: stack, repo layout, conventions, where to look first |
|
Runtime topology + deploy pipeline: what runs where in production, images, CI, ports, auth across tiers |
|
Test suites (Vitest main + epic, Go Bazel), how to run them, and which CI workflows gate them |
|
Performance guardrails: bundle budgets, synthetic probes, RUM SLO bands, and rollback trigger policy |
|
The visual system — Radial Avant-Garde Glass (the radial shell/hub/wheel-feed architecture + the Apple-style Liquid Glass material it references): |
|
Checklist + recipes for building pages that look native |
|
RMH Capital leadership (canon) — the firm’s executive committee and six business heads, their titles and remits, plus the rules for writing them |
|
The developer API documentation — guides plus a generated endpoint reference ( |
|
Albums storage architecture (DB + R2/S3) |
|
Coin economy design (implementation plan, largely shipped) |
Operations¶
Location |
Contents |
|---|---|
Current operational runbooks: Go runtime cutover (2026-06-22), Go fleet steady-state deploy (2026-06-23), assets/CDN cutover, and web hotswap rollback (flip Apache back to the previous blue/green color). Follow these for deploy/rollback work. |
|
The Go+Bazel migration book: |
|
Security audits/reports ( |
|
Optimization/build-speed audits and plans (mostly executed) |
Plans & specs (dated snapshots — check dates before trusting)¶
Location |
Contents |
|---|---|
Parity, QOL & customization design (2026-07-20): sixteen features in four pillars — parity must-haves from comparable platforms (lists/custom feeds, unified saves with folders, history & resume, game hubs with reviews + player guides, post awards, wishlists), social & presence (rich presence + friends rail, custom status, close-friends circle, modular profile showcase), QOL & user customization (appearance/accessibility suite, user-authored theme studio + theme economy, home/sidebar layout control, notification matrix + quiet hours, feed controls), and universal search v2. Verified gap inventory, data models, wave prioritization, KPIs. Companion to the 2026-07-15 and 2026-07-19 docs |
|
Platform expansion design (2026-07-19): twelve features specified as deltas over shipped systems — Arcade Pass (per-game daily challenges), Creator Studio (multi-tier memberships + dashboard), live Spaces, cross-game party system, RMHEvents + RSVP, replays-as-content, P2P cosmetic marketplace, gifting v2, weekly digest email, AI concierge, onboarding “First Week” arc, shareable stat cards. Includes a verified ground-truth inventory of what already exists, data models, wave-based prioritization, KPIs. Companion to the 2026-07-15 doc |
|
Cross-system feature ideas design doc (2026-07-15): six features that compose existing systems — Tournaments Hub, Wager Matches, self-referential prediction markets, creator coin→value bridge, AI personas as residents, unified live-ops season + spectating/”Guess the ___”. Data models, economy loops, prioritization (RMHLadder “Career Mode” excluded — owned separately) |
|
Sitewide Liquid Glass redesign design doc (2026-07-14): glass as the material system — tokens, elevation tiers, realism/reactivity/performance specs, per-page coverage incl. library/studio/shop/admin, phased rollout |
|
The main archive of dated design specs + implementation plans (~75 files, |
|
Older dated plan/design pairs (dream-rift, rmhmusic, rmhcode CLI, terraform/helm migration, farming sim) |
|
Full rewrite design & implementation spec (2026-07-18, machine-readable): target architecture, database domain-schema redesign, async backbone, frontend decomposition, exact deletion inventories, and a dependency-ordered task graph (R0–R5) with per-task verify/acceptance/rollback |
|
Scalability & future-proofing audit (2026-07-17): what breaks at 10x–100x users/data across DB, feed/social, caching, realtime, infra, frontend, and security — with a phased roadmap |
|
CI/CD speed audit (2026-07-17): measured timings for the 79-workflow fleet, deploy-pipeline latency breakdown, redundancy map, and phased recommendations (parallel deploy gate, |
|
Cross-cutting audit + phased roadmap (2026-06-30) |
|
Mobile audit — findings implemented 2026-06-29 (historical) |
|
Feed/timeline scaling plan |
Per-feature docs¶
Location |
Feature |
|---|---|
RMHBox party games — largest doc set: |
|
Altair strategy game — implementation, multiplayer, balance patch history |
|
App design docs (rmhtube |
|
|
Game design docs |
Alex, the Discord tamagotchi pet (now implemented in |
|
Generated book projects (architecture textbook; Library content) — content artifacts, not code docs |
⚠️ Known-stale docs (do not trust these claims)¶
These predate the Next.js → TanStack Start migration and/or the Go cutover:
Any reference to a repo-root
specs/directory — it was deleted; the legacy AI-agent game specs it held (vega.mdand friends) are gone with itrmhtube/features.md— 2025 roadmap for a now-shipped app (its stack line is now correct, but it still describes intent rather than the shipped feature set)Older design docs in
rmhbox/,plans/,misc/, and the textbook chapters mention Next.js in historical context — the routes/stack described there map toapp/routes/+ TanStack Start today../go-services/FOUNDATION.md— apkg/API reference; the removedpkg/events/pkg/realtimesections were cut, but treatgo-services/CLAUDE.mdas canonical (go-services/README.mdwas refreshed to the current 3-service-in-prod reality)Anything claiming production runs PM2 — production is Docker Compose with a blue/green web hotswap (see
architecture.md)
Fixed in the 2026-07-29 audit: the stack lines in void-breaker/specs.md,
temple-of-joy/game-design.md and rmhtube/features.md now name TanStack
Start. temple-of-joy/ was rewritten again on 2026-07-30 alongside the game
itself: game-design.md describes the current economy, and the four docs that
described the superseded one (patch-1.md, patch-2.md,
content-expansion.md, implementation-plan.md) were deleted. The repo-root specs/ directory this file used to point at no longer
exists — the reference was removed rather than repaired.