Docs Overview
How PVERSE documentation is structured across Docs, Whitepaper, Foundation, Game Lane, Game Systems, Token, Market, Affiliate, Infrastructure, Security, and Reference.
What these docs are
PVERSE Docs describe how the platform is designed to behave across participation, gameplay, token structure, market systems, affiliate systems, infrastructure, security, and reference layers.
Docs explain. Systems operate. Configuration defines numeric truth. Status surfaces observed state. Each page should live in one canonical lane so the documentation set remains traceable, stable, and easier to maintain.
How to use this documentation
- New reader: start with Start Here and follow the guided path.
- Need a full navigation map: open Docs Map.
- Need boundaries: read Protocol Boundaries.
- Need documentation rules: read Versioning Policy and Conventions.
- Need recent documentation changes: see Docs Changelog.
- Need fast lookup: jump to Starter Index or Index (By Topic).
Documentation structure
The documentation is organized into lanes. Each lane has a different responsibility. Keeping concepts in their canonical lane keeps the platform easier to understand, operate, and evolve without turning the docs into duplicated noise.
DOCS
Meta-documentation for how the docs themselves are organized, versioned, and maintained.
WHITEPAPER
High-level protocol, world, token, market, infrastructure, and security design intent.
FOUNDATION
Platform participation, access structure, season framing, rollout, and entry model.
GAME LANE
Gameplay philosophy, economy shape, balance policy, safety assumptions, and symbolic layers.
GAME SYSTEMS
Concrete gameplay systems and deterministic in-platform mechanics.
TOKEN
Token design, control logic, supply structure, reserves, bridges, and token-side security model.
MARKET
External token market behavior, liquidity, trading state, order flow, and market-side controls.
AFFILIATE
Referral system structure, attribution, commissions, settlements, campaigns, partner policies, and anti-abuse.
INFRASTRUCTURE
Implementation and operations layer: services, payment engine, addressing, auth, sessions, observability, and reliability.
SECURITY
Security policy, trust and integrity systems, privacy handling, cookies, payment integrity, and disclosures.
REFERENCE
Fast lookup and support navigation across the documentation set.
System layers (mental model)
PVERSE can be understood as layered responsibilities. The documentation mirrors these layers to keep concepts clean and easier to trace.
- Protocol intent → Whitepaper
- Participation and rollout → Foundation
- Gameplay philosophy → Game Lane
- Gameplay mechanics → Game Systems
- Token structure → Token
- External market behavior → Market
- Affiliate system and attribution → Affiliate
- Implementation and operations → Infrastructure
- Security and integrity → Security
- Lookup and navigation → Reference
Canonical placement rules
Each concept should live in one canonical lane. If it needs to be mentioned elsewhere, link to the canonical page instead of duplicating the full explanation.
- Accounts → Foundation
- Discovery / Mining / Refining / Forging → Game Systems
- Karma framing → Game Lane
- Guild mechanics → Game Systems
- Token supply and allocation → Token
- DEX, liquidity, and market structure → Market
- Referral codes, attribution, and commissions → Affiliate
- Payment Engine, Sessions, and Observability → Infrastructure
- Trust score and Privacy → Security
Recommended reading paths
New reader
Developer / builder / operator
Player / systems reader
Documentation status
- Docs version: v1.2
- Base path: /docs
- Canonical URLs: absolute, with trailing slash
- Navigation source: lane-based docs tree with lane-local prev/next behavior