Current static capability
Static claim education can describe a future review sequence, official-source checks, and safety boundaries.
Wallet authentication is disabled for this environment. No wallet provider is requested and no signature is requested.
Vitality app preview
Static module workspace. Live actions remain approval-gated.
Claim controlled preview
Review the planned claim pathway without wallet connection, eligibility lookup, allocation lookup, contract execution, signatures, transactions, distributions, or token movement.
Static controlled preview only. No wallet connection, RPC provider, live on-chain or contract read, balance or treasury read, signature, claim, reward, staking, charging, payment, or token action is active.
Continuity path
This route remains static and safe. Use the continuity links to return to the app command surface, compare module context, and verify status before assuming any feature is active.
Claim preview depth
This route should prepare the future claim experience without exposing any claim button, entitlement result, eligibility read, wallet read, or token action.
User question
What would a future claim flow need to explain before any action exists?
Current preview state
Static claim education only. The route can explain future review stages, safety requirements, and approval gates while keeping all claim actions unavailable.
Product readiness education
This is a static product sequence. It explains what exists now, why live capability remains unavailable, and what must be approved before any future activation.
Current static capability
Static claim education can describe a future review sequence, official-source checks, and safety boundaries.
Why this remains unavailable
No campaign, wallet lookup, allocation lookup, proof check, claim status, signature, transaction, or token movement is connected.
What must be approved next
An approved campaign policy, verified data source, secure claim architecture, independent validation, and release approval must exist first.
Step 1
Available in this previewUnderstand the proposed verification, review, safety, and final-action stages without activating them.
Step 2
Intentionally unavailableNo eligibility, allocation, entitlement, claimable amount, proof, or transaction result is produced.
Step 3
Separate approval requiredAny future claim capability requires approved policy, data, contracts, security evidence, and release controls.
Readiness state legend
No user-specific result
This sequence describes product readiness only. It does not evaluate you, your wallet, an account, eligibility, entitlement, allocation, or claim status.
No live result is produced and no personal evaluation is performed.
Future flow
Outline a future sequence such as source verification, eligibility review, safety confirmation, and final action gate without enabling any step.
Status
Avoid displaying pending, approved, rejected, claimable, available, or countdown states until a real approved backend and policy gate exists.
Safety
Keep this route free of claim buttons, transaction prompts, signatures, wallet reads, balances, or token transfer logic.
Safe boundaries
Continue review
These links stay inside the static controlled-preview layer and do not activate wallet, claim, reward, staking, charging, payment, treasury, or token actions.
25H route continuity polish
These pathway groups help users move through the static app preview without implying any live wallet, chain, balance, treasury, claim, reward, staking, charging, payment, or token action.
Start at the dashboard, then move into the ecosystem and route status layers before reviewing preview modules.
Use contracts, treasury, and safety pages to understand the static source-of-truth boundary before any future live capability.
Review wallet, rewards, claims, and charging as inactive preview modules with informational links only.