Operating rules

Zetaverse operations

The detailed operating tables behind the Business model summary.

Operating layers and service deliverables

The Zetaverse operator's work is organized into six layers, with materials to pass from each step to the next. Actual feature availability will be described in operating updates.

Readiness assessment and matching criteria

The proposed assessment records evidence, development needs and fit for each brief. It does not set follower count as the sole pass condition or prescribe one score or weighting for every campaign.

Monetization paths and commercial terms

The direction is to define the brand's problem and the work to be delivered first, then agree compensation and settlement for that scope. Training prepares creator supply; registration or training participation is not treated as brand revenue.

How campaign economics would be assessed

The proposal is to separate business compensation from creator payments, media spend and expenses administered on behalf of others, and to record direct production and operating costs and time spent for each campaign. The whole campaign budget would not be presented as platform revenue or profit.

Operating decisions would consider business compensation after separating pass-through payments, less direct costs borne by the business from that compensation, alongside time spent. Direct costs considered would include contractually borne creator compensation, production, localization, operations and payment costs, without subtracting already separated pass-through payments twice. Detailed categories would follow the contracts and accounting treatment, with revisions, non-payment, cancellation, creator replacement and cross-border work also assessed.

Repeat brand demand, reductions in sourcing and review time for similar campaigns, and the ability to cover direct costs would inform expansion. NVEX reward budgets would be recorded separately from business payments and direct costs so token transfers are not confused with cash revenue or profit.

Performance measurement and matching feedback

The proposed approach agrees objectives, calculation rules, measurement periods and source data at campaign start, then records results on the same basis. These definitions are proposals, not achieved results or confirmed numerical targets.

Token economy operating details

The following proposed rules guide checks of payouts, service supply, refunds and budgets. Total payouts count each actual reward payment without deducting returns. A payout group collects people rewarded in the same period for observation. Service capacity, group analysis and payout limits are approval policies, not an implemented automated enforcement engine or smart-contract control.

Distribution: only for verified contributions

Registration, wallet linking, holdings and trading volume alone do not earn rewards, and there is no holding interest or staking yield. Payouts link approved budgets to the operator's review records.

Proposed initial services and catalog

Proposed prices, capacity and the first quarterly budget are in "Stage 1 pilot figures" in Token economy. The proposed catalog would publish the following before launch. Fan access is not an initial service; it would be considered separately after Stage 2 rights agreements and delivery conditions are in place.

Proposed creator reward operations

Reward integration starts with reviewing work against campaign-specific terms and recording the basis for payment. The following is a proposed model for the NVEX Foundation and the operator to agree; amounts, schedules and final responsibilities would be announced with operating conditions.

Proposed token-pilot measurement definitions

Counterparties, release and total outflows across all pools

Complete this control table before spending. Proposed shares remain unchanged, but a pool does not spend while annual/quarterly plans and total outflow limits without deducting returns are unset. Same-nature contribution rewards share the annual total reward payout cap regardless of source pool.

Proposed token flow and reallocation

The flow is approved quarterly reward budget → reviewed payout → voluntary creator order → direct NVEX ecosystem receipt → confirmed delivery and refund/dispute closure → eligible base-model reallocation. Direct-receipt exceptions count only contractual returns actually received.

Separate cash flow and service costs

These are proposed fund flows once agreements and funding are secured, not a statement of confirmed brand revenue or cash support today.

Returning service tokens to the foundation does not create cash for staff, facilities, editing or localization. Token receipts and reallocation would not be presented as new market demand or cash revenue. Additional rewards would not be expanded before service costs, refund budgets and capacity are secured.

Decisions required for allocation and payout caps

These are the items to settle before confirming the proposed allocation in Tokenomics and starting the first distribution. It does not change current allocation or lockup facts; approved quantities and schedules would be reflected after separate decisions and disclosure.

Proposed exchange of campaign results

The design maintains a boundary between reviewing source campaign evidence and verifying token payouts.

Exchange permissions, change and correction history, duplicate prevention and retention scope are items to agree with the operator. Personal and commercial source data would be handled within the scope needed for the work; public disclosures would distinguish information approved for payout and transaction reporting. This does not describe a currently operating automatic review or settlement integration.

Proposed collaboration and handoffs

Proposed service receipt · return · shutdown responsibilities

Operating-policy revisions and document · PDF references

Routine reward, catalog and quarterly-budget changes use separate policy revisions rather than rewriting the whitepaper each time. Structural, rights or allocation changes that alter the text require a new whitepaper version and disclosure.

Pilot exit and partnership shutdown handling

Confirmed unpaid additional rewards would be handled by the parties and funding specified in campaign approvals and agreements. Accepted service bookings would be fulfilled as agreed or handled under the disclosed same-quantity refund process. Exceptions for completed work and gas would be limited to advance consent. Refund reserves for related bookings and disputes would not be reallocated. Exit notices would identify the cutoff for new requests, payout, booking and refund contacts and deadlines, and support and appeal channels.

Unused NVEX in a wallet would remain at the holder's discretion. Ending a partnership would not by itself expire tokens or guarantee cash buyback or replacement services.

Optional card and payment infrastructure

Crypto cards and payment rails in the business materials are optional areas for review to support creator payouts and cross-border commerce. Items to assess include issuer and payment-provider roles, countries supported, KYC/AML, fund flows and settlement, conversion, fees and limits, errors, loss, cancellations and user information handling. Providers, conditions and whether to launch would be determined and announced separately, distinct from the NVEX website's current wallet ownership verification and balance lookup.

Stage 1 building blocks

Evidence for moving from Stage 1 to Stage 2

The proposed gate is for the operator to gather the following evidence before selective expansion, rather than advancing on sign-up scale alone. Review periods and numerical thresholds would be set using pilot data and contractual conditions.