Skip to main content

Public Product Docs

Purpose​

Public product docs explain current user-facing VRDex behavior in plain language.

Audience:

  • profile owners
  • community submitters
  • people evaluating what VRDex is for
  • partners who need product behavior, not implementation history

What Belongs Here​

  • current product behavior
  • user-facing trust and claim explanations
  • profile, community, event, world, and discovery usage guidance
  • privacy and opt-out explanations
  • concise integration overviews that do not require implementation details

What Does Not Belong Here​

  • speculative roadmap branches
  • rejected alternatives
  • Terraform/provider setup details
  • internal implementation notes
  • agent workflow notes
  • raw planning dumps

Current State​

Most existing docs are still planning or engineering-heavy. Move material here only when it describes behavior a normal user or public partner can rely on.