Genesis

Overview

Genesis defines how early public participation is represented inside PVERSE. It explains how entry becomes a recorded participation outcome, how allocation records are initialized after verification, and how those records connect to later vesting and live status visibility.

This page is descriptive rather than promotional. Its purpose is to define the Genesis category as part of the system record, clarify how it fits into the broader foundation layer, and preserve a stable interpretation of historical participation over time.

Scope

The Genesis category is intended to clarify how early public participation is recorded, interpreted, and administered within the broader foundation model of the platform.

• early public participation as a structured system category
• initialization of allocation records after verified participation
• linkage from Genesis outcomes into vesting and operational state
• relationship between Genesis records and live status interpretation

Core Model

The core model treats Genesis as an administrative participation classification with operational meaning. It defines how verified entry becomes an authoritative record and how that record is carried forward without retroactive rewriting.

• Genesis is a participation category with record-level meaning
• verified participation initializes allocation records
• vesting governs downstream schedule behavior on authoritative records
• live status reflects current treatment without rewriting past Genesis outcomes

Operational Behavior

Genesis participation moves through an operational path that begins at an entry surface, passes through verification, creates an allocation record if valid, and then becomes governed by vesting schedules and live status references. The category exists to define that path clearly inside the foundation layer.

Any later policy updates, clarifications, or operational changes apply forward only. They may affect future behavior and interpretation, but they do not silently mutate historical Genesis participation records that were already created under prior valid conditions.

Constraints

• Genesis should not be interpreted outside current operational entry and verification rules
• numeric allocations, schedules, and caps belong to SSOT and enforced code paths
• historical Genesis records must remain auditable after later platform changes
• future policy changes apply prospectively and do not retroactively rewrite prior participation

Integrity Considerations

Genesis is also an integrity boundary. It distinguishes valid participation records from informal assumptions, ensures downstream vesting and status treatment is anchored to authoritative records, and preserves a stable historical trail as the platform evolves.

• verified participation should remain inspectable as part of the system record
• vesting and status should operate on authoritative Genesis records rather than narrative context alone
• corrections or clarifications should appear as forward administrative actions, not hidden retroactive rewrites

Future Expansion

As PVERSE expands, Genesis may connect to richer participation reporting, deeper allocation visibility, more explicit administrative references across treasury and status systems, and clearer cross-links between early public participation history and later operational phases.

Summary

• Genesis defines the early public participation category in PVERSE.
• Its role is to connect verified participation to allocation initialization and vesting behavior.
• Live status interprets current operational treatment without rewriting historical Genesis records.
• The category is administered under forward-only rules that preserve auditability.