Skip to main content

Planning Docs

Planning docs capture product, architecture, roadmap, and backlog decisions before they are promoted into stable public, developer, or engineering docs.

Core planning set​

  • docs/planning/research.md - ecosystem scan and adjacent-code notes
  • docs/planning/product-spec.md - MVP scope, user flows, and product rules
  • docs/planning/product-direction.md - durable product compass, current niche, homepage posture, privacy stance, and development pattern
  • docs/planning/architecture.md - suggested system design, data model, and integrations
  • docs/planning/prd.md - product requirements draft for v1 and near-term expansion
  • docs/planning/agent-integration-surface.md - external agent-consumable VRDex skill, API, website navigation, and MCP direction
  • docs/planning/public-api-and-mcp-platform.md - executable plan for public API, API tokens, OAuth apps, rate limiting, Swagger/OpenAPI docs, and hosted/private MCP
  • docs/planning/homepage-discovery-direction.md - homepage, search/discovery, event-calendar, privacy, personalization, and persona direction
  • docs/planning/unified-search-views.md - unified search architecture, typed purpose-specific views, and DJ Lookup compatibility direction
  • docs/planning/personas.md - internal behavioral personas, VR Johnny taste lens, evidence limits, and public-copy review contract
  • docs/planning/jobs-to-be-done.md - prioritized user goals, journey matrix, product-concept boundaries, and filter/preset decision rules
  • docs/planning/ui-quality-direction.md - cross-app UI quality, public profile, auth/account, submission, streaming, and status-surface direction
  • docs/planning/calendar-integration.md - Google Calendar import/export/sync direction for event workflows
  • docs/planning/restreaming-media-control.md - restreaming, VRCDN-first media control, worker architecture, CDN economics, and Discord operator-control direction
  • docs/planning/genre-graph.md - genre ontology, alias normalization, and recommendation graph direction
  • docs/planning/seed-import-model.md - reviewed partner/list seed-import model and fake fixture shape
  • docs/planning/mock-profile-fixtures.md - mock profile fixture strategy, consented showcase allowlists, and group representation direction
  • docs/planning/onboarding-seed-access.md - minimum viable seed-import, private lookup, beta access, and handoff onboarding path
  • docs/planning/world-discovery.md - world pages, creator attribution, active-world discovery, and creator-commerce boundaries
  • docs/planning/marketplace-api-research.md - marketplace sync gate, provider posture, and disallowed storefront data
  • docs/planning/engineering-strategy.md - stack, testing, verification, and agentic factory plan
  • docs/planning/docs-strategy.md - Docusaurus and source-of-truth documentation plan
  • docs/planning/epics.md - phased epic breakdown for v0.5, v1, and v1.5
  • docs/planning/issue-seeding.md - how to split epics into GitHub issues and milestones
  • docs/planning/dependency-map.md - hard/soft dependency map across the seeded backlog
  • docs/planning/issue-drafts.md - drafted GitHub issue bodies captured from planning work

Working rule​

  • keep planning decisions here instead of leaving them only in chat
  • when backlog structure changes, update docs/planning/epics.md, docs/planning/issue-seeding.md, and docs/planning/dependency-map.md together where practical