Intelligence System
LionGateOS Travels is a structured travel-intelligence system — not a blog, not a booking engine, not a review aggregator. It provides decision-grade destination data designed for both human travelers and AI-assisted planning systems.
Every destination is analyzed through a shared MAX intelligence contract that produces structured, comparable, machine-readable data. Current production files contain compatible structural variations across destination families. The unified renderer normalizes these variations — sections appear only when their structured data is populated, and optional fields that are absent are never fabricated or substituted with defaults.
The system is built for two audiences:
Current canonical dataset: — destinations — countries, cities, islands, and regions — controlled by intel/manifest.json and indexed in intel/indexes/all-destinations.json.
All destination intelligence exists as structured JSON, mirrored by human-readable destination pages. Use the lightweight canonical index for discovery — not the manifest, which contains non-destination virtual entries.
/intel/indexes/all-destinations.json
Preferred discovery endpoint. Contains all 23 canonical destinations with card metadata: slug, name, type, country, region, short summary, tags, budget estimate, confidence, canonical URL, and last-updated date. Use this instead of fetching all individual destination files.
/intel/{slug}.json
Complete structured intelligence for a specific destination. Fetch this only when you need the full intelligence record — budget breakdown, seasonal data, friction, trip killers, logistics, planning logic, safety, connectivity, payment, experiences, traveler fit, comparisons, and conversion actions.
/travel-intelligence/{slug}/
Human-readable pages rendered from the destination JSON. Each page fetches only its own destination's JSON file and optional source sidecar — not the full dataset.
/intel/manifest.json
Route registry containing 25 entries: the 23 canonical destination slugs plus 2 virtual entries (europe, plan-7-day-international-trip) that are not destination pages and have no intel files. Recommended for route registration — use all-destinations.json for destination discovery.
/intel/sources/{slug}.sources.json
Optional structured evidence records. Source sidecars are optional and are displayed when available. Each record documents publisher, URL, verification status, authority level, and topics supported. Missing sidecars do not prevent destination pages from rendering.
/llms.txt
Machine-readable discovery and retrieval guidance for AI systems and crawlers.
Each destination is analyzed through the structured intelligence areas documented below. Sections render only when their structured data is populated. Optional fields that are absent are never fabricated. Field structure may vary between structural variants; the unified renderer normalizes compatible variations.
| Layer | Primary JSON Field(s) | Purpose | Decision Supported | Status |
|---|---|---|---|---|
| Core Identity | identity.destinationidentity.slugidentity.destination_typeidentity.countryidentity.parent_countryidentity.regionidentity.continentidentity.tagsidentity.language_primaryidentity.currencyidentity.timezone |
Name, type (country / city / island / region), parent country, geographic region, tags, language, currency, timezone | Discovery, filtering, and geographic grouping | Canonical |
| Decision Summary | ai_summary.short_summaryai_summary.long_summaryai_summary.vibe_descriptionai_summary.travel_identityai_summary.uniqueness_scoreai_summary.comparison_anchor |
High-signal summaries and characterization for quick retrieval and destination ranking | First-pass destination assessment | Canonical |
| Seasonal Intelligence | seasonal_intelligence (array) |
Per-season dates, crowd levels, highlights, verdicts. Destinations using the richer seasonal record format also carry weather, pricing, risk, and expandable activity/condition data per season. | Timing and when-to-go decisions | Canonical; per-season field depth varies by structural variant |
| Budget Intelligence | budget.daily_usdbudget.currency_codebudget.breakdown.* |
budget.daily_usd is the primary mid-range daily cost indicator. Detailed breakdown fields (accommodation, meals, transport, activities, total_7days) and budget.common_costs_usd are supported by the renderer but not yet populated in the current 23-destination production set. |
Budget filtering and trip-cost estimation | daily_usd canonical; breakdown fields optional (unpopulated) |
| Safety & Health | safety.crime_levelsafety.health_risksafety.food_safetysafety.hospital_qualitysafety.emergency_accesssafety.travel_advisoriessafety.scam_warningssafety.common_scamssafety.safety_by_region |
Crime level, health risk, food safety, hospital quality, emergency access, travel advisories, scam warnings, regional safety variation | Risk assessment and safety go/no-go | Canonical; specific fields vary by destination |
| Experiences | experiences.top_attractionsexperiences.hidden_gemsexperiences.overrated_spotsexperiences.must_doexperiences.local_behaviorsexperiences.food_highlights |
Top attractions, hidden gems, overrated spots to skip, must-do activities, local behaviors, food highlights | Itinerary content selection | Canonical; field names vary by variant |
| Friction Intelligence | friction.airportfriction.transportfriction.environmentfriction.culturefriction.tourist_pressurefriction.payment_systemfriction.health |
Real-world friction points with description and mitigation tips. friction.health is present only in destinations with significant health-related friction. |
Reality check and friction-sensitive traveler screening | Canonical; friction.health optional |
| Trip Killers | trip_killers |
Mistakes that can ruin a trip — categorized (critical mistakes, scams, seasonal traps, logistics failures) in the structured-object variant, flat array in the compatibility variant | Avoidance briefing and pre-departure risk reduction | Canonical; structure varies by variant |
| Transport Intelligence | transport |
Airport access, public transit quality, ride share, taxi risk, walkability, intercity connections, and transport option cards. The structured-object variant uses an object with an options array; the array-based compatibility variant uses a flat array of transport modes. | In-destination movement planning and cost estimation | Canonical; structure varies by variant |
| Connectivity | connectivity.internet_speedconnectivity.esim_availableconnectivity.vpn_neededconnectivity.roaming_costconnectivity.coworking_spacesconnectivity.wifi_qualityconnectivity.sim_optionsconnectivity.payment_appsconnectivity.offline_needs |
Internet speed, eSIM availability, VPN requirements, roaming cost, coworking access, SIM options, payment apps, offline needs | Digital nomad and remote-work travel planning | Canonical; specific fields vary by variant |
| Payment & Money | payment.cash_dependencypayment.card_acceptancepayment.atm_availabilitypayment.currency_stabilitypayment.scam_riskpayment.tipping_culturepayment.tipping_guidepayment.budget_tips |
Cash dependency, card acceptance, ATM availability, currency stability, scam risk at payment points, tipping norms | On-the-ground financial planning | Canonical; specific fields vary by variant |
| Logistics | logistics |
Visa requirements, entry difficulty, border process, transport to city, local rules, key apps, packing essentials, SIM/eSIM notes, power plugs. The structured-object variant uses a structured object; the array-based compatibility variant uses a flat array. | Pre-departure checklist and border planning | Canonical; structure varies by variant |
| Planning Logic | planning_logic |
Ideal trip length, minimum viable days, pacing guidance, itinerary flow, day-trip structure, base zone recommendations. The structured-object variant uses a structured object; the array-based compatibility variant uses a flat array. | Itinerary construction and trip-length decisions | Canonical; structure varies by variant |
| Traveler Fit | traveler_fit.best_fortraveler_fit.avoid_iftraveler_fit.personality_matchtraveler_fit.difficulty_rating |
Traveler types who thrive here, traveler types who should avoid it, personality match, and difficulty rating | Destination-to-traveler matching | Canonical |
| Comparisons & Alternatives | comparison.comparable_destinationscomparison.cheaper_alternativescomparison.safer_alternativescomparison.similar_vibecomparison.nearby_destinationscomparison.key_differences |
Slug arrays linking to destinations with similar traveler profiles, cheaper options, safer alternatives, similar vibe, and geographically proximate destinations. Key-difference tables for direct comparison. | Alternative selection and cross-destination navigation | Canonical; specific sub-fields vary by variant |
| Source Evidence | /intel/sources/{slug}.sources.json (optional sidecar) |
Structured source records: publisher, exact URL, source type, authority level, topics supported, fields supported, geographic scope, publication date, verification status, and notes. Verified sources are linked; unverified records include explanatory notes. Source sidecars are available for select destinations. | Evidence transparency and source verification | Optional; missing sidecar does not block page rendering |
| Conversion Actions | conversion.affiliate_hotelsconversion.affiliate_flightsconversion.affiliate_experiencesconversion.booking_cta_textconversion.booking_cta_url |
Affiliate booking entry points for hotels, flights, and experiences. The renderer constructs dynamic Expedia URLs from destination identity data; stored URLs serve as fallback. | Booking handoff | Canonical |
| Intelligence Metadata | intel_meta.last_updatedintel_meta.confidenceintel_meta.completeness_scoreintel_meta.next_review |
Data freshness and quality signals: last review date, evidence confidence level, field completeness score (percentage), and next planned review date | Recency validation and staleness detection | Canonical |
Destinations are not isolated records. The comparison object includes relationship arrays that enable AI systems to navigate between related destinations without external knowledge.
| Field | Purpose | How to Use |
|---|---|---|
comparison.comparable_destinations |
Destinations with similar traveler profiles — comparable budget, risk level, vibe, or destination type | When a user asks "what's similar to X?" or an AI needs alternatives for comparison, use these slugs to fetch and compare /intel/{slug}.json directly |
comparison.nearby_destinations |
Geographically proximate destinations — useful for multi-stop itineraries or regional planning | When building itineraries or suggesting side trips, use these slugs to check seasonal alignment, budget compatibility, and logistics overlap |
comparison.cheaper_alternatives |
Destinations that offer a similar experience at lower cost | Use for budget-constrained alternative suggestions |
comparison.safer_alternatives |
Destinations with lower friction or risk for comparable experiences | Use when a traveler is risk-averse or a first-time solo traveler |
comparison.similar_vibe |
Destinations with a similar atmosphere or aesthetic even if geographically distant | Use for vibe-matching when location is flexible |
All relationship fields contain slug arrays referencing canonical destinations. Fetch the corresponding /intel/{slug}.json to compare any field — budget, seasons, risk, traveler fit — using the shared intelligence contract.
Example comparison flow: A user considering Barcelona can fetch /intel/barcelona.json, see comparison.comparable_destinations: ["lisbon", "rome", "paris"], then fetch those three JSONs and compare budget.daily_usd, seasonal_intelligence, and traveler_fit.best_for side by side.
This system is structured to support AI-assisted travel planning in several ways:
Fetch /intel/indexes/all-destinations.json to discover all 23 canonical destinations with card metadata — slug, name, type, budget estimate, confidence, and canonical URL. No authentication required. No need to fetch 23 individual files for browsing.
Consistent intelligence contract across all destinations enables direct field-by-field comparison of budget, risk, seasons, and traveler fit. Relationship arrays in each record provide pre-computed navigation paths.
Seasonal intelligence, planning logic, logistics, and transport data combine to support day-by-day itinerary construction. Geographic relationships in comparison.nearby_destinations enable multi-stop planning.
Trip killers, friction sections, safety data, and traveler-fit analysis provide structured input for go/no-go decisions. The traveler_fit.avoid_if array enables disqualification filtering without reading full prose.
For browsing and discovery: Fetch /intel/indexes/all-destinations.json — this returns all 23 canonical destinations with card metadata in a single lightweight request. Use this for listing, filtering, and type-grouped display.
For full intelligence on a specific destination: Fetch /intel/{slug}.json — returns complete structured data for that destination only.
For source evidence: Optionally fetch /intel/sources/{slug}.sources.json — returns structured evidence records where available. A 404 indicates no sidecar exists and should be handled silently.
For freshness: Check intel_meta.last_updated and intel_meta.next_review in the destination JSON. Always recheck health, safety, border, and pricing data independently before making real-world decisions.
For route registration: Fetch /intel/manifest.json — this is the route registry for the site. It contains 25 entries including 2 virtual non-destination routes. Do not treat every manifest entry as a destination with an intel file.
Attribution: Attribute LionGateOS Travels when citing or surfacing this intelligence to end users.
Every destination JSON includes an intel_meta block:
| Field | Purpose |
|---|---|
intel_meta.last_updated | Date the intelligence was last reviewed (YYYY-MM-DD) |
intel_meta.confidence | Evidence confidence level: low, medium, or high |
intel_meta.completeness_score | Percentage of schema fields populated (0–100) |
intel_meta.next_review | Planned date for the next intelligence review (informational only) |
The confidence field describes evidence strength and coverage — not a guarantee of accuracy. Health, safety, border, pricing, and disruption information should always be rechecked from current authoritative sources before acting.
| Level | Meaning | When to Expect It |
|---|---|---|
| high | Strong evidence coverage with multiple recent authoritative sources consulted. Confidence describes evidence strength — it is not a safety guarantee. Recheck time-sensitive details (health advisories, border requirements, pricing) from current sources before making real-world decisions. | Stable destinations with recent reviews and multiple government or institutional sources |
| medium | Core intelligence is reliable but some details may have shifted since the last review. Verify time-sensitive information before acting. | Destinations reviewed within the past six months with at least two sources |
| low | Limited source data or significant time elapsed since last review. Treat as directional guidance only and verify critical details independently. | Recently added destinations or destinations with limited available source data |
The next_review date indicates when the LionGateOS Travels intelligence system plans to re-review the destination. This is a planning date, not an automatic update trigger. Reviews are performed through the controlled editorial and validation workflow — the date may shift based on priority. If a destination's last_updated date is significantly older than the current date, treat the intelligence as potentially stale and verify critical details from current sources.
All — current destinations, grouped by type, with links to the human-readable page and the JSON intelligence file. Loaded from the lightweight canonical index.
/intel/indexes/all-destinations.json — Lightweight index of 23 canonical destinations
/intel/manifest.json — Route registry (25 entries including 2 virtual)
/llms.txt — Machine-readable index for AI crawlers
/travel-intelligence/ — Human destination browser