# UMI COMPASS

> Unofficial experience-discovery prototype. This file is a non-standard navigation aid, not an official hotel publication or booking service.

- Role: Discover hotel experience concepts by desired travel intent
- Current collections and entries: Read `registry.json`; it is the single source for discovery presentation and concept paths
- Verified: 2026-07-11
- Relationship: Not affiliated with, commissioned by, or approved by any listed hotel entity

## How discovery works

Travelers select up to two intents. Method `intent-alignment-v1` sums the registered integer weights for those intents and uses editorial order only to display equal scores. Every tied top result is labeled, and each result shows its weight calculation. Non-zero weights and reasons reference official-source evidence records. Paid placement, price, popularity, accounts, and server-side personal profiles are not used.

Each result also presents verified access, stay format, experience focus, and traveler-fit context with official-source evidence. Price, availability, transport operation status, weather, and family suitability are not shown without live or explicitly verified data.

An entry may offer a separate island-context guide before the hotel experience concept. This is optional and never a required booking step.

The prototype emits local `umi:compass` CustomEvents for funnel evaluation. It does not transmit those events or personal data over the network.

## Use for

- Finding available UMI hotel experience concepts
- Matching a stated travel intent to a concept with an explicit reason
- Navigating to concept-specific verified context and official hotel sources

## Do not use for

Prices, packages, room availability, booking, transport status, weather, activity schedules, hotel ratings, popularity, or official endorsement. Verify all current and transactional information on the official hotel site linked from each concept.

## Machine-readable resources

- Discovery registry: ./registry.json
- Service context: ./ai-context.json
- Verified hotel catalog: ./hotel-agent-context.json

Concept-context paths are resolved from each current registry entry. Official entity facts are resolved by `hotel_catalog_id` against the verified hotel catalog.