Your cruise day, in the right order.
Major Wave v71 adds redemption recovery evidence: passengers can distinguish a retryable request, an authoritative failure, an unknown outcome and a confirmed completion without Cruisivo turning uncertainty into a duplicate redemption.
Main Theatre · Deck 5
Dinner · Ocean Grill
Meet Deck 7 · 4 joined · 1 pending
Optional Treasure Quest
1,240 pts · 1 unlock
Ship Map
Interactive deck discovery, wayfinding and nearby experiences.
What's On
Shows, dining, activities and live events in one passenger feed.
Play
Quests, trivia, treasure hunts and partner games with future StreamSIX integration points.
Rewards
Earn, unlock and redeem cruise-line rewards and partner offers.
Keep rewards useful without pretending a sample balance is live.
Label points as verified, last-known or sample so passengers can tell what the number means.
Keep selected shows, dining and partner experiences together for the current voyage and future planning.
A saved reward is a passenger choice, not proof of redemption, inventory or payment.
Preserve preference context while keeping cruise-line loyalty authority separate from Cruisivo.
Know what is saved, eligible, confirmed, and actually redeemed.
A passenger choosing a reward records interest only. It does not reserve inventory or spend points.
Show the source and freshness of points, tier, voyage or partner rules before presenting a reward as eligible.
Inventory, price and redemption remain VERIFY until an identified cruise-line or partner system confirms them.
Only an authoritative transaction response may be labelled redeemed. Failure or uncertainty stays visible and retry-safe.
Retry safely without spending twice.
A failed pre-submit check may be retried only when no authoritative transaction was accepted.
Show the identified system response and keep the reward unredeemed rather than guessing success.
If connectivity drops after submit, stop automatic retry and mark VERIFY until the authoritative system can be checked.
Only a matching authoritative transaction response can close the request as redeemed.
Verify the source before you retry.
Name the cruise-line or partner system that supplied the balance, eligibility or transaction result.
Show when authoritative evidence was last checked so a cached result is never presented as current.
A confirmed redemption keeps its transaction/reference evidence separate from the passenger's tap or local intent.
An unknown or stale result must be rechecked against the authoritative source before another spend is allowed.
See what happened before deciding what to do next.
Keep the passenger request separate from any cruise-line or partner transaction.
Record which authoritative system received the request and when it was sent.
A timeout, stale receipt or conflicting result stays VERIFY and blocks automatic replay.
Close the timeline only when fresh authoritative evidence confirms completion or failure.
Your live cruise feed
Featured live show. Save to My Night or navigate there.
Dining availability and Cruisivo member offer.
Join a ship-wide challenge and unlock reward points.
Play, earn and continue the experience after the voyage.
Build tonight from evidence, not guesses.
Wave v68 makes every proposed plan easier to trust: passengers can see whether a time or offer is ship-published, partner-supplied, saved from an earlier view, or still needs verification before acting.
Saved show with one-tap directions from the current deck.
Dining reservation window and Cruisivo member benefit.
Optional social game placed around the passenger’s real plans.
Flag overlapping plans before the guest commits.
Highest-confidence planning evidence when the ship or cruise line is the identified source.
Useful only when the partner identity and offer details are visible to the passenger.
Keep the last known detail readable, but show that it may be stale and should be refreshed.
Unknown source, conflicting time, missing availability or stale evidence stops the action flow.
Take the ship experience ashore without losing the passenger.
Keep the group’s return location, time and simple directions visible.
Surface cruise-line-approved excursions, dining and partner offers.
Show a clear ship-time reminder before all-aboard.
Port quests and partner rewards feed the same Cruisivo wallet.
The digital layer between the passenger and the ship.
Passenger App → Ship Digital Twin / Map → Activities & Venues → Games & Quests → Rewards Wallet → Offers & Commerce → Loyalty Profile → Next Voyage
Illustrative annual infrastructure revenue per deployed ship target.
Illustrative annual installs based on 150K annual passenger opportunities and approximately one-third adoption.
Illustrative cruise-line infrastructure charge per passenger install.
One tap to the next useful cruise action.
Cruisivo now puts the passenger’s most likely next actions in one compact rail so the experience feels like a usable companion instead of a long product demo.
See the next show, dining slot or activity.
Build my nightSave plans and catch conflicts before they happen.
Find my groupJump to shared plans, meet-up points and availability.
Rewards + walletCheck points, saved experiences and continuity.
Where am I?Open the day compass for current deck and next move.
Need ship staffUse the official crew handoff boundary for service or operational help.
Know the ship clock, the all-aboard boundary, and when to head back.
Show ship time separately from local port time so passengers do not silently assume the clocks match.
Keep the cruise line’s published all-aboard time visible beside the passenger’s own planned return target.
Present a conservative personal return buffer as planning guidance, never as a replacement for official ship instructions.
If time-zone, itinerary or operational information is stale or unclear, stop presenting it as current and direct the passenger to crew or official cruise-line channels.
Prototype boundary: Cruisivo does not claim authoritative vessel time, live gangway status, automatic time-zone correction or operational integration unless those feeds are actually connected and verified.
Save the few return facts that matter before you leave the ship.
Keep the cruise line’s published ship-time boundary visible and label who supplied it.
Keep a separate personal target so guidance can never be mistaken for the official deadline.
Keep the last loaded meet-up point, ship name and terminal/pier note together for quick reference.
Show when the card was last refreshed. Stale or uncertain information is marked VERIFY, never silently treated as live.
One return plan everyone can understand before the group splits up.
Keep one simple place and ship-time visible for the whole group before anyone leaves.
Show who has acknowledged the plan without pretending Cruisivo has live location or messaging.
Each passenger can plan an earlier target while the official all-aboard boundary remains separate and authoritative.
If a person, time or meet-up detail is unclear, mark VERIFY and use official crew or cruise-line channels.
Prototype boundary: readiness is a planning state, not proof of a passenger’s location, safety, receipt of a message or ability to return on time.
Keep the group plan useful when the signal gets weak.
Keep the most recently loaded meet-up place and ship-time visible instead of showing a blank state.
Show when information was last updated so cached details are never presented as live truth.
Use a clear manual refresh action when connectivity returns; do not imply background sync that does not exist.
If plans conflict with cruise-line instructions, passengers follow crew, muster, medical, security and operational guidance.
Prototype boundary: this wave does not claim live location, offline messaging, background synchronization or cruise-line system integration.
Show pilot systems + technical history
Historical pilot modules and browser-local contracts v7–v56 are preserved in the previous WordPress revision and GitHub release history. The active v64 front door does not migrate or delete those existing browser-local keys. This collapsed section is intentionally concise so the passenger experience is not buried under implementation history.
Release-truth reconciliation: v58 was an older page checkpoint, v60 introduced the action rail, v63 reconciled release truth, v64 added low-connectivity group reliability, and v65 is the current human-facing checkpoint. Older technical checkpoints remain rollback evidence rather than the current product version.
Development prototype • 4BR • Major Wave v71.0 • Redemption recovery evidence • Economics are illustrative targets, not guaranteed results.