TwoMore Documentation Index
Auto-generated by
scripts/generate-docs-index.mjs(runyarn docs:generate). The complete, grouped index of every Markdown doc underdocs/— 158 files. Do not hand-edit; edit the source docs and regenerate.
Cockpit & work area
What's active, blocked, and how to proceed — plus the status legend.
- Current Documentation State — Generated
- Current Project State — Generated
- Doc Status Conventions — Active
- External Blockers Register — Active
- Full status — Active
- How the Cockpit Works — Active
- index — Active
Wireframes
The app’s wireframes — one config-driven surface per section, plus screens and the rating model.
- ELO Tier System — Cross-Rating Mapping Specification — Active
- Rating System v2 — Specification — Active
- Screen Blueprint — TwoMore (투마) — Reference
- Surface System Unification — Clubs + Sessions (info-models, projections, canonical bindings) — Active
- Wireframes — Active
Roadmap & launch
The R1→R4 plan, the current slice, launch gates, evidence, and the operating workflow.
- Agent prompt templates — Curated prompt scaffolds for common agent tasks on TwoMore. Each template:
- Change Routing Workflow — Active
- Claude Agent Ingestion Brief — Active
- Engineering Soundness Masterfile — Active
- Maestro E2E — Active
- Multi-Agent Operating Model (Claude Code + Codex) — Active
- Performance budgets — Reference
- Pre-launch Checklist — Active
- Production Readiness Review — Active
- R1 Activation Source Pack — Active
- R2-0 Admin Workflow Teardown — Active
- Release Evidence Ledger — Active
- Release Versioning And OTA Workflow — Active
- Slice-Completion Loop — Active
- Template: Add a new feature screen — Reference
- Template: Add a new mutation hook — Reference
- Template: Add a new query hook — Reference
- Template: Execute A Roadmap Slice — Reference
- Template: Performance investigation — Reference
- Template: Refactor shared code — Reference
- TwoMore Roadmap — Active
- TwoMore Roadmap Implementation Plan — Active
Product
What we're building and why — the feature map, product spec, and market/opportunity research.
- Match Rotation Engine Specification — Active
- Progression System — Design Specification — Draft
- Signal System — Unified Alerts, Banners, Badges, Notifications — Reference — Locked spec, ready to implement (all open questions resolved, see §14)
- Sports Club Administration Opportunity Audit — Active
- Tennis Playability Index (TMI) v2 — Specification — Reference — Current
- Terminology Guide — TwoMore (투마) — Reference
- Trust & Reputation System — Specification — Draft v2
- TwoMore App Functionality Map — Active
- TwoMore Market And Revenue Research — Active
- TwoMore Platform Architecture — Features, Trust, Subscriptions — Reference — Final Draft
- TwoMore Product Spec Sheet — Active
- TwoMore Revenue Model — Complete Specification — Reference — Final Draft
- Voice & Tone Guide (Korean UX Writing) — Active
Docs & reference
How we build — conventions, architecture, guides, best-practices, and audits.
- 0001 — Agentic project foundation: 9-layer infrastructure — Accepted
- 0002 — Hexagonal architecture for shared business logic — Accepted
- 0003 — Tamagui as the sole styling solution — Accepted
- 0004 — Supabase as the managed backend — Accepted
- 0005 — Network orchestration protocols (A–K) — Accepted
- 0006 — ESLint ratchet: waiver discipline for new rules — Accepted
- Accessibility (A11y) Standards + Test Plan — Reference
- Agentic Project Foundation — Reference — P0 → P7 substrate shipped (with caveats — see phase table). Active for ratchet shrink + remaining DOC-pla…
- Android Emulator Setup & Running the App — Reference
- Architecture Conventions — Active
- Architecture Decision Records (ADRs) — This directory holds the canonical record of major architectural decisions made on TwoMore.
- Authentication — Native SDK Implementation — Active
- Best Practices Reference — Comprehensive best-practices guides for TwoMore, covering all aspects of React Native (Expo SDK 55) app development. …
- Builds & Deployment — Reference
- Club Surface Conventions — Active
- Component Conventions — Active
- Conventions › Match Generation — Reference — Spine established 2026-07-14 (owner-directed). Only the recording axis is active; every other axis is mod…
- Credentials & Environment Variables — Reference — Current
- Data & Hooks Conventions — Active
- Debugging Workflow — Reference — Current
- Expo Push Notifications — Reference
- External APIs & Services — Index — Reference
- Foundational Schema Audit — Tennis Standards & Future-Proofing — Reference — Planning artifact, NOT a migration batch. 8 of 8 domains have verified, adversarially-reviewed research.
- Foundational-Schema Decisions — Reference — Decided positions + library selections + ordered implementation plan. This is the ACTIONABLE resolution o…
- International Data-Model Foundation — Reference
- Korean Market Conventions — Active
- Matchmaking Pipelines — Status Tracker — Active — living tracker, update in place as fixes ship
- Naver Local Search API (via Naver API Hub) — Reference
- Naver Maps Deep Links — Reference
- Networking Conventions — Active
- Networking, Caching & Data Layer Best Practices — Reference
- Notification Conventions — Active
- PortOne v2 payments — setup guide — Reference
- Pretendard fonts — TwoMore — The official TwoMore repo expects four OTF weights at:
- React Native (Expo SDK 55) Best Practices: UI/UX, Accessibility, Navigation — Reference
- React Native Performance & Memory Management Best Practices — Reference
- Research Methodology — Multi-Dimensional Grounding — Reference
- Review Checklist — semantic guidance reviewers must apply — Reference
- Scale + Connection Limits — Supabase Postgres + Edge Functions — Reference
- Security & Authentication Best Practices — Reference
- Session Surface Conventions — Active
- Shared Client Architecture — Active
- Staged OTA Rollout Procedure — Active
- State Management, Architecture & i18n Best Practices — Reference
- Status & Recruitment Conventions — Active
- Supabase — Reference
- Tamagui & Styling Conventions — Active
- Testing, Error Handling, Monitoring & Build/Deploy Best Practices — Reference
- TwoMore Design System — This design system packages the classic grass-court green, Toss-minimal visual language of TwoMore v2 — its tokens an…
- UX-audit residual queue — owner decisions — Active
- Venue Metadata Ingest — runbook & status — Reference
- Wireframe + Spec Buildout — every screen, grounded in code — Draft
- Wireframes System — Active
- Working-Model Retro — honest collaboration feedback — Active
Archive & history
Retired and superseded docs, session logs, and the milestone archive — history only.
- Alert-Model Wiring Contract (2026-07-11, owner-approved) — Archived
- Audit Remediation — Problem Spaces & Solution Architecture (2026-07-11) — Archived
- Autonomous Sweep Log - 2026-04-24 — Archived
- Autonomous Wave-2 Run Ledger (2026-07-12, owner asleep) — Archived
- B1 — Clubs Domain: Adversarial BACKEND Audit — Archived
- B2 — Sessions/RSVP: Adversarial BACKEND Audit — Archived
- B3 — Payments (Backend) Adversarial Audit — Archived
- B4 — Matches + Rating (Backend) Adversarial Audit — Archived
- B5 — Attendance/Trust + Dues (Backend) Adversarial Audit — Archived
- B6 — Venues + Weather: Adversarial Backend Audit — Archived
- B7 — Platform Plumbing (Backend) Adversarial Audit — Archived
- B8 — Auth/Identity (Backend): Adversarial BACKEND Audit — Archived
- Backend Wiring Plans — 2026-07 Adversarial Audit Synthesis — Archived
- CLAUDE.md Milestone Archive — Archived
- Club Growth Completion Slices — Archived
- Counsel Prep Brief — TwoMore v2 Privacy Policy + Terms of Service — Archived
- Device Setup — EAS Build + OTA Updates — Superseded
- Drift Prevention — Mechanical Enforcement Strategy — Archived
- Elo Rating System Specification — Superseded
- Home State Model — Specification — Archived
- i18n audit — TwoMore — Archived
- Implementation Plan — 2026-07-11 Whole-App Audit Remediation — Superseded
- Implementation Roadmap — 2026-07 Audit Remediation — Archived
- Matchmaking Pipeline & Registry — Implementation Spec — Archived
- Networking Foundation — Phased Implementation Plan — Archived
- Onboarding Redesign Specification — Archived
- Overnight session summary — 2026-04-18 — Archived
- Profile / Engagement / Offline / Clubs / Pickup / Settings / Aliveness — TwoMore production roadmap — Archived
- PS1 — Access Control & DB Hardening — Archived
- PS1 Profiles PII Split — Implementation Spec (research-grounded, 2026-07-12) — Archived
- PS10 — Records & Analytics UX — Archived
- PS11 — Platform Guardrails — Archived
- PS12 — Engineering Streamline (final phase) — Archived
- PS2 — Payments & Settlement Integrity — Archived
- PS3 — Session & RSVP Lifecycle — Archived
- PS4 — Match & Rating Integrity — Archived
- PS5 — Dues & Attendance — Archived
- PS6 — Clubs & Membership Lifecycle — Archived
- PS7 — Identity, Account & Consent — Archived
- PS8 — Notification & Signal Surfacing — Archived
- PS9 — Venues & Discovery — Archived
- Rebuild Log — Archived
- Stack Decisions — 2026-04-17 — Archived
- Tamagui Patterns — TwoMore v2 — Superseded
- TwoMore Rating System — Complete Summary — Superseded
- U1 — Home + Notification Center — Adversarial Audit — Archived
- U2 — Clubs: Adversarial UI/UX Audit — Archived
- U3 — Sessions: Adversarial UI/UX Audit — Archived
- U4 — Matches (경기): Adversarial UI/UX Audit — Archived
- U5 — 기록/Records: Adversarial UI/UX Audit — Archived
- U6 — Discovery: Adversarial UI/UX Audit — Archived
- U7 — Auth/Profile/Settings + DM: Adversarial UI/UX Audit — Archived
- U8 — Dues (회비): Adversarial UI/UX Audit — Archived
- UI Primitive Drift Audit — 2026-07-19 — Archived
- UI/UX Design Specs — 2026-07 Adversarial Audit Synthesis — Archived
- v1 Learnings — Archived
- Whole-App Semantic-Block Adversarial Audit — Orchestration Plan (2026-07-11) — Archived