Overview

Overview

The Foundation lane defines the participation administration layer of PVERSE. It specifies the operational interfaces and constraints used for Genesis and Founders participation, including how entry is recorded, how allocation records are initialized, how vesting is administered, and how live status is communicated.

Foundation exists so participation can be understood as an operational system rather than as a loose collection of landing pages. It describes how participation categories work, where operational responsibility begins and ends, and how changes are applied forward-only without retroactively rewriting past participation history.

Scope

Foundation covers participation administration and the operational policies surrounding it.

• participation categories such as Genesis and Founders
• entry and record-creation surfaces for allocation initialization
• vesting schedules, lockup administration, and release handling
• season boundaries, roadmap ordering, and live participation status

Core Model

The Foundation model is operational and forward-only. Participation is not treated as an abstract promise. It is treated as an administrative flow with explicit records, schedules, statuses, and policy boundaries. Each step should remain auditable and interpretable without collapsing into protocol or market semantics.

• participation categories define how a participant enters a governed flow
• entry creates or links allocation records under explicit rules
• vesting and status tracking control how those records evolve over time
• future policy updates apply prospectively and do not silently rewrite past records

Operational Behavior

In normal operation, a participant enters through a defined Genesis or Founders surface, the system creates or links an allocation record, the applicable vesting or lockup logic becomes active, and status surfaces reflect the live administrative state. Foundation pages describe that path from participation category to current state.

Under future operational changes, such as schedule refinements, status clarifications, or entry-flow updates, Foundation follows a forward-only model. Historical participation records remain intact. Changes affect future behavior, future interpretation boundaries, or future status handling rather than rewriting what was already recorded.

Constraints

• Foundation does not define protocol guarantees, ledger finality, or token-market behavior
• Foundation does not replace SSOT for numeric or configuration truth
• Foundation should describe participation administration, not gameplay mechanics or infrastructure internals
• if a rule concerns protocol truth, in-world mechanics, or execution infrastructure, it belongs to the Whitepaper, Game Lane, or Infrastructure respectively

Integrity Considerations

Participation administration only remains trustworthy if records and status surfaces can be interpreted consistently over time. Foundation therefore emphasizes explicit categories, explicit flows, and explicit forward-only boundaries. Administrative changes should never blur the distinction between operational policy and immutable historical participation records.

• past participation records are not retroactively rewritten
• operational status must remain readable and attributable to current policy state
• participation administration should stay separate from protocol guarantees and gameplay mechanics

Participation Surfaces

Genesis and Founders are participation categories, not protocol definitions by themselves. Foundation pages define how those categories are administered, how they move through operational flow, and how their live state is presented.

Policy Boundary

Foundation pages describe participation administration and operational policy boundaries. Protocol guarantees are defined in the Whitepaper. In-world mechanics are defined in Game Lane. Infrastructure pages describe the systems that execute the operational flow. Foundation sits between those layers as the administrative participation surface.

Future Expansion

This section may expand as PVERSE adds more detailed participation phases, richer allocation-state explanations, additional administrative status surfaces, and clearer cross-links between policy and live operational state. As it grows, Foundation should remain the canonical lane for participation administration rather than drifting into protocol, gameplay, or infrastructure ownership.

Summary

• Foundation defines the participation administration layer of PVERSE.
• It covers Genesis and Founders entry, allocation record creation, vesting, season boundaries, and live status.
• Foundation is forward-only: updates apply prospectively and do not rewrite past participation records.
• Protocol guarantees stay in Whitepaper, while gameplay and infrastructure remain in their own lanes.