Service Cross-Link Map
Purpose
Use this page as the high-level map between VRDex services, docs, and implementation surfaces. Link from service-specific pages back to this map when readers need to understand how one area affects another.
Public Product Surfaces
| Surface | Purpose | Related Docs |
|---|---|---|
| Web app | Public profiles, discovery, submissions, events, worlds, auth, and account pages. | Product spec, Search discovery, Profile access and claims |
| Docs site | Human and agent-readable source of truth. | Docs strategy, Public docs, Developer docs, Engineering docs |
| Public API | Future versioned read surface for structured consumers. | Public API posture, VRDex MCP read tools |
| Partner-agent skill | Product-facing integration guidance for external agents. | Partner agent skill, OpenCode adapter |
Hosted Infrastructure
| Service | Purpose | Related Docs |
|---|---|---|
| Vercel | Hosted web deployments, preview deployments, staging helpers. | Vercel preview deployment, Self-hosting and IaC |
| Convex | Application data, functions, auth integration, local backend verification. | Convex bootstrap, Convex environments |
| AWS SES | Auth email sender and domain email verification. | SES auth email, AWS service baseline |
| AWS S3 | Planned private profile asset storage baseline. | AWS service baseline |
| Route 53 | DNS records for hosted domains, SES, and future provider-owned records. | AWS service baseline, Self-hosting and IaC |
| PostHog | Hosted product analytics and feature-flag direction. | Product analytics and feature flags, Self-hosting and IaC |
| GitHub Actions | Baseline checks, CodeQL, hosted health checks, and deployment automation. | Contributor workflow, Definition of done |
| Terraform | Reproducible provider configuration and hosted bootstrap state. | Self-hosting and IaC, infra/terraform/README.md |
Cross-Linking Rule
- Service docs should link to their owning implementation docs and to adjacent services they depend on.
- Product-facing pages should link to developer or engineering detail only when the reader needs deeper context.
- Developer docs should link to public behavior and implementation constraints so integrations preserve trust, visibility, and provenance.
- Engineering docs should link back to public/developer surfaces when a decision changes what users or external consumers can rely on.