The world we curate — the architecture behind the experience
← Back to Home

TravelWell OS v5.0 · The architecture under the experience

TravelWell is an OS, not a directory.

Six layers, two intelligence dimensions, three platforms. Every relationship between every entity is modeled, weighted, and validated — so the system can think about the world the way an expert advisor does.

The architecture under the experience

Most travel sites organize content. We organize meaning.

Behind every page on TravelWell.World is a six-layer operating system that treats travel the way a great human advisor does — emotionally informed, operationally precise, and always aware that every choice the traveler makes ripples through every other choice. This is the architecture investors, partners, and host-agency members are reviewing.

Layer one through six

The six layers of TravelWell OS

Layer 01

The locked demand anchors

25 Special Interests

Each SI is a Travel World — its own emotional archetype, partner stack, season window, safety profile, and editorial voice. The 25 SIs span the General Travel volume layer and the Premium + Ultra-Luxury universes.

Layer 02

Geographic routing framework

11 Global Regions

Not political borders — how a traveler actually moves through the world. Each region carries gateways, peak seasons, country sets, and a recognizable mood. Caribbean (01F) is home territory.

Layer 03

Service delivery channels

The Nine Wells

Fly · Stay · Eat · Move · Gear · Beauty · Insure · Do · Ship. Every booking belongs to exactly one Well. Every trip touches several. The Wells are the body-system metaphor that organizes commerce.

Layer 04

Intelligence layer

13 v2.0 Engines

Content · routing · destination · activity · seasonal · memory · deep-link · monetization · safety · personalization · campaign · AI sync · interest. Each engine has a single responsibility and a clear contract with the others.

Layer 05

Data canon

H1–H8 Schemas

Eight schema families govern every object in the system — SIs, Regions, Destinations, Providers, Wells, Safety Cards, Deep Links, Monetization. Every entity ID-bears and is routed through schema validation.

Layer 06

The relational intelligence layer

Cross-World-Reference-Map★ Backbone

Every relationship between two ID-bearing entities is a row in this map. Each row carries an Emotional Weight (1-7) and an Operational Weight (1-7). This is what makes TravelWell behave as a unified ecosystem instead of a collection of pages.

The Cross-World-Reference-Map

Every relationship carries two weights.

Behind every page sit thousands of relationships — SI to Region, Region to Destination, Destination to Safety Card, Safety Card to Insurance Provider, and so on. Each relationship carries two numbers, not one. This is what makes the system emotionally intelligent.

Dimension 01

Emotional Weight

How strongly this relationship shapes meaning, identity, or emotional experience. Scored 1-7. Categorized Low / Medium / High.

Example: A child-friendly snorkel beach’s link to Family Travel is Emotional-7. The memories last decades.

Dimension 02

Operational Weight

How critical this relationship is to workflows, dependencies, or system behavior. Scored 1-7. Categorized Low / Medium / High.

Example: A safari camp’s link to its host conservancy is Operational-7. Without the lease, the camp does not exist.

Both numbers travel through the system together. Personalization, ranking, governance, and risk analysis all consult both dimensions. This dual-weight architecture is what separates an OS from a website.

Three platforms, one architecture

Where the canon lives

TravelWell separates record, meaning, and experience. Each platform does one job exceptionally well. None can drift from the others — the architecture is duplicated as authoritative reference in all three.

System of record

Coda

The master Cross-World-Reference-Map lives here. All computation, weight scoring, validation, and audit logging. The source of operational truth.

System of meaning

Notion

The narrative layer. Filtered views per World. Editorial canon, voice, and tone live here so the OS reads as a brand, not a database.

System of experience

GitHub + Next.js

The traveler-facing render layer. A downstream consumer of the map. Never bypasses the schema for ad-hoc relationship modeling.

“The bridge between Worlds, the engine behind global insight, and the foundation for the long term.”

— Architecture of record · spec/cross-world-reference-map.md

By the numbers

What the architecture organizes today

25
Special Interests
11
Global Regions
9
Wells
13
v2.0 Engines
H1–H8
Schema families
262
Vetted Providers
129
Destinations

See the architecture in action.

Open any Special Interest, Region, or Well. Every page renders directly off the canon described above.

If It’s Travel… Travel Well.