Summary

This PR adds the initial product vision and MVP planning docs for the VR Office – Privacy-First Virtual Workspace inside the vr-office directory. It aligns the community around a clear problem statement, solution, and scope so contributors can quickly understand what we’re building and how to help.

What’s included

• /vr-office/README.md
  • Defines the core vision and problem statement (remote work productivity paranoia without surveillance).
  • Describes the proposed solution: VR office with spatial presence, proximity chat, in-VR screen sharing, and status indicators.
  • Documents target users and primary use cases.
  • Highlights the key differentiator: privacy-first architecture with aggregate metrics only and zero content capture.
  • Outlines tech stack, success metrics, milestones, and contribution entry points.
• /vr-office/docs/mvp-scope.md
  • Provides a detailed MVP scope for VR Office v0.5.0.
  • Breaks down in-scope features:
    • Multi-user VR office (Unity + OpenXR + XRI + Photon PUN 2)
    • Proximity voice with distance falloff (Agora / Photon Voice)
    • In-VR screen sharing to virtual desk monitors (Agora Video)
    • Presence status system (Available / Focus / DND)
    • Admin dashboard with aggregate-only metrics (Next.js + Supabase)
    • Auth via Auth0/OIDC
  • Clearly documents explicit non-goals for MVP:
    • No content surveillance (keystroke logging, screenshots, productivity scoring, etc.)
    • No mobile/standalone VR for MVP (PCVR only)
    • No >16 concurrent users per room
    • No separate video calls, real-time whiteboards, or advanced collab tools
  • Maps features to milestones (0.1.0–0.5.0, 0.6.0 Fusion migration).
  • Defines “Definition of Done” for the MVP.

How this addresses the tracking issue

This PR:

• Documents the Core Vision in /vr-office/README.md:
  • Problem, solution, target users, and privacy-first differentiator.
• Introduces a detailed MVP Scope in /vr-office/docs/mvp-scope.md, including:
  • Core features, tech stack, and explicit non-goals.
  • Milestone alignment and sizing (issues, contributors, timelines).
  • Clear, measurable success criteria (FPS, latency, screen-share time-to-first-frame, and privacy guarantees).

Together, these docs make it possible for any new contributor to understand the VR Office product direction and MVP in < 5 minutes, satisfying the clarity and measurability requirements from the tracking issue.

Linked issue

Closes #61