One research layer. Many specialist destinations.
Destination Command Center sits before the transaction. It answers the question, compares the tradeoffs, and preserves the context. When the traveler is ready to choose, reserve, book, or plan, the relevant specialist site takes over.
1 · Understand
DCC owns questions, research, comparisons, logistics, constraints, and pre-purchase decisions.
2 · Choose
Focused destination and excursion sites narrow the actual experience or route.
3 · Buy / reserve
Transaction and marketplace sites handle current price, availability, terms, and execution.
4 · Plan
Where useful, Cruise Promenade turns selected cruise choices into a shared group plan.
UNDERSTAND -> CHOOSE -> BUY_OR_RESERVE -> PLAN
A DCC page should solve the research problem on its own. Outbound links are the next action, not the reason the page exists. The specialist site owns its own commercial truth. We do not duplicate transaction pages across domains.
Earth OS & Destination Command Center Architecture: Satellite sites provide focused user journeys, while Fulfillment remains strictly governed. Fulfillment is replaceable across each approved partner, owned checkout, direct operator handoff, or partners like GetYourGuide based on live market truth.
The 16-site suite
Each domain has one primary job. That separation is what lets the network become interconnected without becoming duplicate content.
Live DCC → specialist handoffs
These edges are generated from the same registry that renders the decision-guide pages, so the public site and the machine-readable topology cannot quietly drift apart.
Cruise-port authority queue
These are upstream authority opportunities. They are not automatically booking pages: DCC earns the search visit first by answering the port-day decision.