Token Model

Overview

The Token Model defines the PVR token layer as a representation + enforcement surface for protocol-defined rights and records. The token layer is intentionally separated from the in-world economy: it does not create value through emissions. Instead, it records and enforces allocation, vesting, and transfer/liquidity constraints under forward-only rules.

This design preserves auditability and prevents UI, sentiment, or market interpretation from becoming canonical truth. The token layer exists to express and enforce protocol-defined entitlements, not to replace world logic or create inflation-driven incentives.

Scope

This page specifies token-layer behavior only: supply discipline, allocation recording semantics, transfer boundaries, vesting anchoring, and liquidity gating as auditable controls. Market behavior, liquidity strategy, router surfaces, and security boundaries are defined elsewhere and are not implied by token allocation or vesting.

• Defines fixed-supply token-layer rules and allocation recording semantics.
• Defines vesting anchoring and forward-only unlock behavior.
• Defines explicit transfer and liquidity activation boundaries.
• Defines evidence standards when USD valuation affects token-layer outcomes.

Core Model

PVR functions as an ownership and settlement layer. It represents protocol-defined entitlements and their unlock state over time, and exposes a constrained transfer surface aligned with activation controls. The token layer is not an emission-driven reward mechanism.

• Ownership representation: allocational rights expressed as token-level entitlements.
• Settlement surface: a unit for transfers once enabled by explicit policy.
• Constraint enforcement: transfer and liquidity controls MAY restrict behavior until activation.
• Forward-only record discipline: outcomes are written as auditable records rather than mutable UI state.

Operational Behavior

The token layer follows a controlled transition model. Allocation records, market activation, transfer-state changes, liquidity-state changes, and vesting ticks are treated as append-only events executed under explicit policy and verifiable evidence. Market activation defines T₀, and vesting schedules reference that anchor rather than interface time.

If USD valuation affects tiering, reporting, gating, settlement, or any canonical outcome, the system MUST preserve enough oracle evidence to reconstruct the valuation independently. Determinism and replay safety take precedence over convenience.

Constraints

• Fixed supply: the token model does not depend on continuous emission loops.
• Explicit enablement: transfers and liquidity exposure are enabled states, not assumptions.
• Append-only history: corrections are represented as new events, never silent rewrites.
• Truth hierarchy: verifiable logs and controlled execution are authoritative; UI is informational.

Integrity Considerations

The Token Model is governed by strict authority separation. Canonical outcomes are produced only by controlled transitions executed against verifiable evidence. If ambiguity arises, the interpretation that best preserves determinism, scarcity enforcement, replay safety, and audit integrity takes precedence.

• Allocation ≠ tradable supply: entitlement does not imply market availability or liquidity.
• Vesting is forward-only: unlocks are append-only events anchored to on-chain activation.
• USD evidence reconstructability: if valuation matters, oracle/feed/round evidence must be reproducible.

Future Expansion

Category-specific vesting schedules, activation policies, and market-layer execution details may evolve through forward-only ruleset updates. Such changes apply prospectively and do not rewrite prior allocations, prior unlock history, or previously recorded evidence. The Token Model remains the stable enforcement contract beneath those future surfaces.

Summary

• The PVR token layer is separated from the in-world economy and does not rely on emission-driven inflation.
• Supply is fixed; distribution is expressed through allocation records and vesting unlock events.
• Transfers and liquidity exposure may be restricted until explicitly enabled by policy.
• If USD valuation is used, it must be reconstructable from recorded oracle evidence under deterministic rules.