Core Loop

Overview

Core Loop defines the canonical gameplay pipeline of PVERSE and the rule boundaries that keep outcomes deterministic, scarcity-preserving, and forward-only. It explains the stage sequence, what each stage consumes and produces, and how outcomes become durable recorded history inside the playable world.

In PVERSE, value does not appear through arbitrary issuance or vague reward emission. It moves forward through constrained transformation. Discovery exposes opportunity. Mining converts that opportunity into bounded outputs. Refining and forging compress value through risk, cost, and conversion rules. Ownership is the endpoint where recorded world history accumulates.

Scope

This page defines the canonical world-action pipeline used by Game Lane and the integrity rules that preserve its meaning across future balancing and seasonal change.

• the canonical stage sequence from discovery through ownership
• what each stage consumes, produces, and constrains
• how structural scarcity is maintained through friction and bounded distributions
• how recorded outcomes remain forward-only and non-retroactive

Core Model

The core loop treats player progress as conversion under constraint. Every stage exists because value must be transformed, not merely handed out. A player interacts with opportunities, tools, time, inventory, and risk, and the world records the result under fixed rules. The loop is therefore both a gameplay system and a world-accounting system.

• value moves forward through constrained conversion rather than inflationary emission
• each stage has explicit inputs, outputs, and rule-defined limits
• recorded outcomes matter more than UI presentation or cached state
• future balance changes apply forward only and do not silently rewrite past results

Operational Behavior

In ordinary play, a player discovers opportunities, mines raw resources, refines or upgrades them through bounded success models, forges higher-form outputs where allowed, and accumulates the resulting ownership as persistent world state. Time, tool quality, inventory capacity, conversion costs, and success rates all shape the path forward.

Under abnormal conditions, the platform may tighten future parameters, close exploit surfaces, or rebalance future outcomes. That is allowed. What is not allowed is retroactively erasing already recorded gameplay history. The world remains coherent because rule changes move forward while historical outcomes remain preserved.

Constraints

• Core Loop does not define protocol guarantees, participation policy, or market activation behavior
• not every numeric parameter should live here; detailed values belong to SSOT tables and narrower pages
• seasonal or structural tuning may affect future outcomes without changing the meaning of past recorded outputs
• if a rule concerns infrastructure, security, wallet custody, or DEX launch operations, it belongs outside the game loop layer

Integrity Considerations

The integrity of the core loop depends on preserving the distinction between world rules and presentation. A UI can lag. A session can expire. A cached page can be stale. None of that changes the actual outcome. Recorded world transitions, produced by system rules, are the authoritative source of truth for the game loop.

• UI display does not establish truth; recorded transitions do
• scarcity must come from world rules, not operator improvisation
• historical outcomes remain preserved even when future parameters are rebalanced

Loop Stage Definitions

Scarcity Mechanics

Scarcity in PVERSE is structural. It emerges from constrained processes rather than inflationary emissions or arbitrary operator reward pulses.

• Time gates: progress requires time and bounded actions
• Conversion costs: refining and forging consume inputs under defined rules
• Bounded distributions: outputs are governed by tables and constraints, not manual edits
• Loss models: failures and partial yields prevent frictionless compounding
• No emission loop: engagement is not sustained by uncontrolled issuance

Forward-Only Balance Updates

Balance adjustments may occur to prevent exploits, stabilize the economy, or address technical constraints. These updates apply to future outcomes only. Past drops, conversions, and ownership records are preserved and are not rewritten retroactively.

Recorded Outcomes

The loop produces recorded outcomes at each conversion boundary. These records exist to preserve historical integrity and to keep outcomes explainable through inputs, constraints, and rule-defined transitions.

• Drop outcome records: mining outputs recorded as results under the active ruleset
• Conversion outcome records: refining and forging outcomes recorded, including failures and partial yields
• Ownership records: inventory state and ownership history preserved once recorded

Future Expansion

This page may expand over time as PVERSE formalizes more detailed progression hooks, inventory friction references, stage-specific anti-abuse controls, and season-aware gameplay modifiers. As the Game Lane section matures, Core Loop should remain the canonical pipeline reference while narrower pages define the economics, balance rules, and safety posture around it.

Summary

• PVERSE Core Loop is the canonical gameplay pipeline: discover, mine, refine, forge, and own.
• Value moves forward through constrained transformation rather than arbitrary issuance.
• Scarcity is structural and preserved through time gates, conversion costs, bounded distributions, and loss models.
• Recorded outcomes remain forward-only and non-retroactive even when future balance parameters change.

Protocol note: This documentation is descriptive, not promotional. It exists to define system behavior and constraints. If updates are required, they apply to future behavior only. Past records are not rewritten retroactively.