Discovery

Overview

Discovery is the first playable stage of the PVERSE game loop. Its role is to evaluate whether resources are eligible to appear in a given context before any extraction takes place. That context may include location pools, time windows, player progression, world state, and protective constraints that preserve long-term economy shape.

This page is descriptive rather than balance-final. It defines meaning, boundaries, and operational flow while leaving exact numeric distributions, cadence values, and constraint parameters to future SSOT-controlled references.

Scope

Discovery defines appearance eligibility inside the Game Systems layer rather than realized rewards or downstream processing values.

• location-based and pool-based resource eligibility before mining
• time windows, player context, and global state as discovery inputs
• safety constraints that preserve scarcity and reduce exploitability
• forward-only discovery evaluation and auditable discovery outcomes

Core Model

The core model is that discovery maps a set of inputs to an eligible resource set. This eligible set is not the same thing as a mining reward. It is the structured output of discovery logic that later gameplay stages consume.

• discovery decides what may appear under valid conditions
• mining decides realized outcomes from the eligible set
• eligibility and realized reward are related but distinct concepts
• policy and balance changes apply to future evaluations only

Operational Behavior

Discovery runs as an eligibility layer within the canonical gameplay pipeline. It evaluates current inputs such as zone, window, progression, and operational locks, then produces a structured result that defines what can appear for the next stage of gameplay.

In practical terms, discovery may be influenced by location pools, spawn windows, cooldown-style controls, season or world state, and anti-farm safety policies. These inputs define what is eligible now, but they do not retroactively rewrite what was eligible in a past window.

Constraints

• discovery does not define mining output amounts, processing yields, or final reward distributions
• protocol guarantees, participation administration, token allocation, and vesting remain outside this page
• numeric parameters such as intervals, caps, and cooldowns belong to SSOT rather than this document
• missed windows, delayed UI, or later policy updates do not retroactively rewrite prior discovery history

Integrity Considerations

Discovery integrity comes from separating descriptive meaning from enforced state. Documentation explains what discovery is, SSOT controls numeric parameters, and code produces auditable eligibility outcomes. This keeps the system understandable while preserving long-term traceability.

• UI may lag or simplify presentation, but authoritative discovery state is server-side
• safety locks and anti-farm rules must be explicit rather than implied by presentation alone
• past discovery outcomes remain auditable even when later balance or policy updates occur

Future Expansion

As PVERSE expands, discovery may connect to richer zone logic, deeper player-state modifiers, live-ops events, dynamic world conditions, and more explicit pool or window references. The conceptual model should remain stable: discovery defines eligibility first, and later stages decide realized output.

Summary

• Discovery is the eligibility layer that determines what may appear before mining.
• It evaluates location, timing, player context, and safety constraints.
• Its output is an eligible resource set, not a final reward.
• All discovery updates follow forward-only interpretation and preserve auditable history.