PVERSE
REFERENCE

Index (By Topic)

Browse the PVERSE documentation set by concept and domain. Use this page when you know what you want, but not which lane owns it.

Published: March 23, 2026
Updated: March 24, 2026
Section: REFERENCE
Navigation-only boundary
This page is a topic index. It does not define rules. Canonical rules live in their owning lanes, and this page only routes readers to them.

Overview

PVERSE Docs can be explored in multiple ways: by role through Starter Index, by structure through Docs Map, and by concept through this page.

Index (By Topic) is useful when you understand the subject you are looking for, but do not yet know whether it belongs to Whitepaper, Foundation, Game Lane, Game Systems, Token, Market, Affiliate, Infrastructure, Security, or Reference.

How this page works

  • topics are grouped by durable concepts, not temporary UI wording
  • each section points to canonical lane-owned pages
  • this page should shorten search time without becoming a second rule surface
  • when a concept expands, the index should point to the correct page instead of duplicating explanation locally
DOCS WHITEPAPER FOUNDATION GAME LANE GAME SYSTEMS TOKEN MARKET AFFILIATE INFRASTRUCTURE SECURITY REFERENCE

DOCS

Documentation structure, boundaries, versioning, conventions, and doc-system maintenance.

WHITEPAPER

Protocol guarantees, system architecture, economic structure, Genesis and Founders framing, token model, market layer, infrastructure, and security-finality intent.

FOUNDATION

Accounts, entry, participation flow, vesting, season framing, and platform rollout structure.

GAME LANE

Core gameplay philosophy, economy framing, balance policy, economic safety, and symbolic systems such as karma and emblems.

GAME SYSTEMS

Deterministic gameplay mechanics: discovery, mining, refining, forging, runes, progression, guilds, marketplace, inventory, subscriptions, and more.

TOKEN

Token-side structure: design goals, utility, supply, allocation, vesting, reserves, bridges, controls, and token security model.

MARKET

External token market behavior: liquidity, DEX integration, market making, order flow, trading controls, trading state, listings, and risks.

AFFILIATE

Referral and partner systems: referral codes, attribution, commissions, settlements, withdrawals, campaigns, leaderboard logic, and anti-abuse policy.

INFRASTRUCTURE

Implementation and operations: services, storage, payment engine, wallet addressing, RPC providers, auth, sessions, observability, runbooks, and limits.

SECURITY

Security and integrity: threat model, account safety, authentication and recovery, trust score, privacy, cookies, disclosures, payment integrity, and risk boundaries.

REFERENCE

Lookup and navigation surfaces: starter paths, topic browsing, definitions, snapshots, FAQ, and changelog routing.

Special use cases

I know my role, not my topic

I need the whole docs tree

I want quick clarification

How to use this index

  • use this page when you know the concept but not the lane
  • once you reach the owning page, treat that page as canonical
  • use Starter Index for role-based routing
  • use Docs Map when you need the full hierarchy
Stability note
Topics and routes may expand over time, but this page should remain a routing surface. If a concept changes ownership, update the pointer to the new canonical page instead of copying rule text here.

Summary

  • Index (By Topic) helps readers find canonical docs pages by concept instead of sidebar order.
  • It improves cross-lane discoverability without taking ownership of rule text.
  • It should stay topic-first, short, and pointer-based.
  • It is most useful when the reader knows the subject but not the route.