100 subject hubs 313 institutions 24 scholarships 1,162,501 searchable units 40 live axes 1,119 trade mandates

⚡ Borderless Living Layer · v138.9

Where you live is now a strategic decision.

Climate, cost, visa, infrastructure, food, safety. Five lenses, fifteen sub-lenses, 2,596 cities across 184 countries — and a journey spine that walks you from "where to live" through "how to work there" to "should I commit?". Multilateral, never bilateral-narrowed.

2,596Cities
184Countries
15Lenses
1082Visa regimes
1,162,501Searchable units
40Live axes

Stage 1 · The fundamental question

Live — where to actually be

The question "where to live" used to be answered by where the work was. That's still partially true, but the calculus has changed. A senior engineer with a remote contract can choose between Lisbon, Tallinn, Bali, Mexico City, or Bengaluru and have substantively different lifestyles for the same dollar income. The trade-offs are real, and they are not equivalent.

The travelogue was built around the practical question of which trade-offs you actually care about. Each city carries 15 intelligence lenses — climate, cost, visa difficulty, English fluency, housing supply, food culture, healthcare quality, internet reliability, distance to major hubs, time-zone alignment, safety, walkability, tax residency rules, business-formation difficulty, and exit liquidity. Browse the cities below and see which ones fit your weights.

2,596cities total
184countries covered
15intelligence lenses
34real-estate cities
26biz-formation cities
~5.3MURL surface

Eight ways into Live

The Live stage runs from /cities/ + /countries/ + /best/ + /listicles/. 2,326 cities × 15 lenses = ~5.3M URL surface at full expansion. 15-lens unique-content generator fires per city × lens combination. Schema: BreadcrumbList, TouristDestination, Place, Article, Dataset.

who

Who is this stage for?

Location-flexible professionals on remote contracts, families relocating for work or schooling, retirees comparing destinations, dual-career couples optimising joint outcomes, students picking student cities. Increasingly relevant as work-from-anywhere becomes a default rather than an exception for professional roles.

what

What does it cover?

2,326 cities, each carried with the full 15-lens intelligence: climate (annual averages + extremes), cost (rent, food, transport, healthcare, utilities, schooling, leisure), visa difficulty for non-citizens, English fluency, housing supply for foreigners, food culture, healthcare quality, internet reliability, distance to major hubs, time-zone alignment for remote work, safety, walkability, tax residency rules, business-formation difficulty, and exit liquidity.

when

When should it be used?

Any planning horizon — short-term test stays of three to twelve months, medium-term anchor stays of one to five years, long-term family relocations of five-plus years. The stage scales the same lens-stack for all three but the weights shift: a test stay weights climate and walkability; an anchor stay weights healthcare and schooling; a long-term move weights tax residency and exit liquidity.

where

Where does coverage extend?

Six continents × 197 countries × tier-one through tier-three cities = 2,326 cities total. Tier-one cities (capitals, major commercial hubs) have the deepest coverage; tier-two regional hubs and tier-three provincial cities have lighter coverage but still complete factsheet base. India is densely covered (289 cities) for principal-context relevance.

why

Why is location now strategic?

Because for a growing professional population, geographic location is a parameter rather than a constraint. A senior engineer with a remote contract can choose between Lisbon, Tallinn, Bali, Mexico City, or Bengaluru and have substantively different lifestyle outcomes for the same dollar income. The trade-offs are real and they are not equivalent — the lens stack is built to make them comparable.

which

Which lenses weigh heaviest?

Depends on the user. For digital nomads: visa-friendliness, internet reliability, time-zone alignment, English fluency, walkability. For families: schooling availability, healthcare quality, safety, climate stability. For retirees: cost level, healthcare access, tax burden, food culture, social infrastructure. The factsheet exposes all 15; the user weights them.

whose

Whose framework underwrites it?

Numbeo (crowd-sourced cost-of-living index), Mercer Cost-of-Living survey (corporate dataset), Expatistan (consumer cross-check), Knight Frank Wealth Report (real-estate), national statistical services (CPI, housing index, crime stats), Speedtest (connectivity), WHO + INFORM (safety + health risk), national ministries (visa rules current), plus AJG editorial composition.

how

How does the stage connect downstream?

Every city factsheet links forward to the Work stage (visa pathway for that city), the Cost stage (full cost-of-living comparator), the Infra stage (safety + climate + connectivity profile), and the Decide stage (head-to-head comparator + listicle generator). The lineage from Live to Decide produces a final shortlist.

Main-site counterpart

Live is the geographic counterpart of School on the main site. Where you live determines which schools, which jobs, and which work pathways are accessible — the lineage upstream of Travelogue.

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV

User POV — for the relocator, founder, student, professional

Eight dimensions

1 · Possibility

In principle, a location-flexible professional can live in any of 2,326 cities across 197 countries — work-from-anywhere remote contracts, digital-nomad visas, family-class accompaniment, and student-visa adjacent paths all create access. The outer envelope is genuinely vast: the same senior engineer can choose between Lisbon, Tallinn, Bali, Mexico City, Bengaluru, or Tbilisi for substantively different lifestyle outcomes at the same nominal salary. The constraint is decision capacity, not city-level access.

2 · Plausibility

Realistically, a relocation-considering candidate who weights the 15 lenses deliberately — climate, cost, visa, English fluency, healthcare, walkability, time-zone — converges to a 10-city shortlist, then to a 2-3 city decision pool, with a defensible quality of life equal to or better than current. The plausibility envelope is wide for high-skill remote workers (perhaps 200 cities are realistic on visa + cost grounds), narrower for in-person workers (perhaps 30 cities given employer geography).

3 · Probability

Most relocation-curious candidates underestimate how much lifestyle quality and salary-purchasing-power they can capture by moving. The probability of net-positive relocation outcome — better life, more savings, equal-or-better professional trajectory — is perhaps sixty percent for high-skill remote workers who deliberate; near-random for those who just take the first job offer. The asymmetry favours deliberate weighting of the 15 lenses against personal context, not generalised "best places to live" lists.

4 · What works

What works: (1) test-staying for three to twelve months before committing to multi-year residency; (2) weighting the 15 lenses against personal context (a family with school-age kids weights schooling and healthcare; a single nomad weights connectivity and visa-friendliness); (3) running the cost-of-living comparator with concrete monthly-budget assumptions; (4) talking to two or three actual residents before booking the move; (5) maintaining an exit option (return-flight reserve, retained domestic banking, registered home address).

5 · What doesn't work

What does not work: (1) committing to multi-year residency before test-staying; (2) using generic "best places to live" lists without weighting against personal context; (3) optimising on one lens (cheap rent OR good climate OR low taxes) at the expense of others — that produces unstable relocations; (4) underestimating relocation friction-cost (banking, healthcare paperwork, shipping); (5) ignoring exit liquidity — some destinations are easy to enter but hard to leave for tax-residency or capital-control reasons.

6 · Common pitfall

The biggest trap at TRAV live stage is committing to multi-year residency before test-staying. The lived experience of a city across one full month differs substantially from the visitor experience across one weekend — air quality varies seasonally, traffic patterns reveal themselves only at school-run timing, neighbourhood noise emerges only at typical-resident hours. Multi-year commitments based on weekend visits are the most common reversal pattern.

7 · Counter-intuitive insight

Counter-intuitively, the city most often optimal for a given relocator is rarely the most-famous city in their target country. The famous cities (London, New York, Sydney, Singapore) are priced into the relocation premium and saturated with similar candidates. The second-tier cities of the same countries (Manchester, Pittsburgh, Adelaide, Penang) often produce better lived outcomes for similar professional roles at materially lower cost.

8 · Highest-leverage move

The single highest-leverage move at live stage is to test-stay in the candidate city for at least one month during the worst-season for that climate — monsoon, winter-extreme, summer-extreme. Most candidates visit during peak season and are surprised by reality. Off-season test-stays prevent perhaps two-thirds of post-relocation regret.

Eight user intents

9 · Who gains most

Location-flexible professionals on remote contracts, families relocating for work or schooling, retirees comparing destinations, dual-career couples optimising joint outcomes, students picking student cities. The constraint is decision capacity not city-level access.

10 · Irreducible essence

The irreducible essence: test-stay before committing; weight the 15 lenses against personal context; prioritise infrastructure dealbreakers over cost preferences.

11 · Optimal timing

Any planning horizon — short-term test stays (3-12 months), medium-term anchor stays (1-5 years), long-term family relocations (5+ years). The lens-stack is the same; weights shift across the three.

12 · Where it matters most

6 continents × 197 countries × tier-1/2/3 cities = 2,326 cities total. India is densely covered (289 cities) for principal-context relevance. Tier-1 cities have the deepest factsheet coverage; tier-3 cities have lighter coverage but still factsheet-complete.

13 · Why misunderstood

Live stage is misunderstood because most relocators treat city choice as residual ("where the work is") rather than primary ("where I want to live"). For increasingly large fractions of the professional workforce, location is now a parameter rather than a constraint.

14 · Highest-leverage sub-paths

Highest-leverage city categories vary by candidate. For digital nomads: Lisbon, Tallinn, Bali, Mexico City, Tbilisi, Bengaluru. For families: Auckland, Vienna, Vancouver, Singapore, Tokyo. For retirees: Porto, Valencia, Penang, Mexican Pacific coast cities, Eastern European tier-2 cities.

15 · Whose advice to trust

Trust: Numbeo cost-of-living index (crowd-sourced, broad coverage), Mercer Cost-of-Living survey (corporate dataset, narrow but accurate), national statistical services, local-resident conversations via LinkedIn outreach or expat forums. Ignore: relocation-marketing companies, single-anecdote I love this city social media posts.

16 · How to proceed differently

Proceed by collapsing the 2,326-city corpus to a 10-city shortlist via the 15-lens factsheet, then to a 2-3 city decision pool via comparator + listicles, then test-stay each finalist for one month. Decide on first-month lived evidence; do not continue analysing past that point.

Developer POV — for the architect, maintainer, AI tool, future contributor

Eight dev dimensions

17 · Data architecture

TRAV live stage composes from cities-essentials.php (2,326 cities with base lens factsheet), cities-global.php (T1+T2 expansion), cities-tier3.php (+426 T3), and 15 lens data files (climate, cost, visa, real-estate, food, safety, infrastructure, etc). Lens-unique-content generator at includes/lens-unique-content.php composes 3 distinct paragraphs per city × lens combination. The live stage card grid surfaces the top T1 cities with lens highlights.

18 · Schema markup

TouristDestination schema on per-city pages; Country schema on per-country hub pages; ItemList of city-cards on stage; Place schema on city profiles. The lens-unique paragraphs are wrapped in CreativeWork schema with about=Place + lens type. Schema graph is keyed on city-slug for discovery.

19 · Internal linking

Live stage links forward to work/cost/infra/decide; outward to /cities/{slug}/, /cities/{slug}/{lens}/, /countries/{country}/. Cross-content injector handles tokens: "live", "city", "expat", "remote", "nomad". Sister-rail cross-link to MAIN (allfrontierglobal.com) for trade-context bridges. Link weaver handles 2,326 city names automatically.

20 · Page-speed posture

Live stage payload ~14 KB. Featured-cities card grid uses CSS Grid auto-fit. Render ~250-420 ms. Lens-unique generator pre-cached at master-refresh cron; runtime cost is array lookup not generation. Per-city pages render at ~200-350 ms.

21 · Mobile UX

City card grid 4-col → 2-col → 1-col responsive. Tap-targets ≥48px. Sticky journey nav. Lens highlights wrap via flex-wrap.

22 · Accessibility

City cards semantic <a>. Lens-highlight pills are <span> with role-text. Heading hierarchy h2/h3/h4. Color contrast AAA body / AA pills.

23 · SEO saturation

Per-city URL: /cities/{slug}/. Per-city-per-lens: /cities/{slug}/{lens}/. Total URLs ~5.3M (2,326 × multiple lens combinations). Canonical per page. Sitemap split: /sitemap-cities.xml + per-lens sitemaps. IndexNow on edit. Schema TouristDestination + Place per page.

24 · Extensibility

New city: append to cities-essentials.php (base) or cities-global.php (T1+T2) or cities-tier3.php (T3). All 15 lens factsheets fire automatically. New lens: more involved — add lens-data file, add lens-unique-content generator clause, add lens-rendering template, add lens-sitemap. New lens ship: ~2-3 hours.

Eight dev intents

25 · Who maintains

Joint. City registry: 2,326 entries; updates rare for new tier-3 additions, periodic for lens-data refreshes (climate/cost/safety quarterly).

26 · What tech stack

Tech: PHP arrays per registry, lens-unique-content.php generator (~340 lines, composes 3-paragraph blocks per city × lens). Helpers ajg_cities_all(), ajg_cities_by_tier(), ajg_cities_lens_data().

27 · When to refresh

Lens data quarterly (climate/cost/safety/infrastructure refresh on quarterly external-data update cycles). City registry rare-edit. Master-refresh cron coordinates.

28 · Where in codebase

Code: cities-essentials.php, cities-global.php, cities-tier3.php, includes/lens-unique-content.php, /cities/index.php, /cities/profile.php, /cities/lens.php.

29 · Why this approach

Why composing 3-paragraph blocks per city × lens at master-refresh time rather than at request time: (1) keeps render-time low; (2) lens combinations stable; (3) cron-time generation amortises composition cost; (4) regen on lens data update.

30 · Which dependencies

Critical: cities-essentials, cities-global, cities-tier3 (all three), lens-unique-content.php generator, city helper functions. Optional: per-city PDF photo galleries, per-city historical-weather time-series.

31 · Whose responsibility

Same ownership. City data verified against UN World Cities + OECD Metropolitan + national-statistics-office data. Lens data sources documented per-lens in lens-unique-content.php header comment.

32 · How to extend

New city: append to relevant tier file. Lens factsheet generation runs automatically via lens-unique-content. New lens: add LENSES constant in lens-unique-content.php + new lens-data file + new lens-route in front-controller.

Stage 2 · The legal infrastructure

Work — visa, tax, business setup

The visa, tax, and business-setup layer is where most relocations actually fail — not because the country is wrong but because the legal framework is incompatible with how you actually earn. A digital-nomad visa sounds romantic until you discover it doesn't permit you to invoice domestic clients. A territorial-tax country sounds attractive until you realise your foreign-source income is also taxable if you spend more than X days there. Read the fine print before choosing the city.

The work layer documents 1082 visa regimes plus tax residency, business formation, and banking access — for each major destination jurisdiction. Each entry distils what the country actually requires (income thresholds, residence days, return-flight timelines) rather than the marketing brochure.

1082visa regimes
22digital-nomad visas
26biz-formation cities
23tax regimes
40+banking pathways
5visa programs deep-dived

Eight ways into Work

The Work stage runs from /visa/ + /tax/ + /business-formation/ + /banking/ + per-city work-stack pages. Twenty-six cities deep; 200-plus visa programmes wide. Schema: BreadcrumbList, GovernmentService, Article, FAQPage.

who

Who is this stage for?

Expat-bound professionals, founders contemplating moving themselves and their company, freelancers relocating to a tax-friendly base, dependents researching the work-rights side of a partner's relocation, and HR/relocation-mobility teams handling employee transfers.

what

What does it cover?

Per-city visa programmes, tax residency rules, business formation feasibility, banking access for foreigners. Twenty-six cities have full work-stack profiles; 200-plus visa programmes are catalogued at programme level. Real-tax-burden modelling for expat-status earners under bilateral treaty relief.

when

When should it be used?

Six to twelve months before relocation. Visa programmes have lead times ranging from one month (Bali B211B) to twelve months (UK Skilled Worker via sponsor). Tax-residency optimisation should ideally be planned six months pre-move to avoid double-residency complications in the year of departure.

where

Where does coverage extend?

Twenty-six cities with the full work-stack: London, Berlin, Amsterdam, Lisbon, Madrid, Dubai, Singapore, Hong Kong, Tokyo, Seoul, Shanghai, Sydney, Auckland, Toronto, Vancouver, New York, San Francisco, Mexico City, São Paulo, Buenos Aires, Bangkok, Kuala Lumpur, Jakarta, Bengaluru, Mumbai, Delhi. Lighter coverage for emerging hubs.

why

Why is the visa class the lever?

Because the visa class determines what you can do, for whom, in what role, for how long, on what tax basis, with what spousal/dependent rights, and with what exit options. Two candidates moving to the same city under different visa classes can have radically different feasibility, cost, and ceiling.

which

Which programme types are catalogued?

Skilled Worker (employer-sponsored), Talent (objective-merit), Digital Nomad (location-flexible income), Investor (capital-deploying), Family-class (spousal/dependent), Retirement (passive-income), Student-post-study, Self-employed/freelance, plus specific-occupation lists (Australia SOL, Canada NOC, UK Shortage Occupation, US Schedule A).

whose

Whose framework underwrites it?

Destination immigration ministries (Home Office UK, USCIS, IRCC, DoHA, MoM, ICA, DHM, etc.), tax-treaty matrices (OECD Model + bilateral treaty texts), national-banking regulators (FCA, MAS, SEC-Bermuda, etc.), AJG editorial cross-checks against successful-applicant cohorts.

how

How does the stage connect downstream?

Every work-city profile links forward to the Cost stage (cost-of-living for the city), the Infra stage (safety + climate + connectivity), and the Decide stage (city comparator). It also links upstream to the main site Jobs and Work stages, where the upstream credentials and visa-eligibility logic sit.

Main-site counterpart

The Travelogue Work stage is the city-level depth that the main-site Jobs and Work stages reference. Together they cover the upstream credentials side and the downstream city-level relocation side of the same decision.

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV

User POV — for the relocator, founder, student, professional

Eight dimensions

1 · Possibility

In principle, every legal-residence-status professional can establish a tax-optimal, visa-secure, biz-formation-feasible, banking-accessible base in any of 26 anchor cities (full work-stack profiled) plus 200-plus visa programmes catalogued. The outer envelope of expat work-stack is wide — Skilled Worker, Talent, Digital Nomad, Investor, Self-employed, Family-class, plus retirement and student-post-study pathways. The constraint is documentation lead time, not pathway availability.

2 · Plausibility

Realistically, a candidate working the work-stack deliberately — checking tax treaty positions before relocating, picking the visa class with the longest exit option not the fastest entry, opening destination banking before relocation rather than after — achieves a stable expat work-stack within twelve to eighteen months. The plausibility envelope is wider than most candidates expect because most underestimate the number of low-friction visa classes they qualify for if they take a moment to map.

3 · Probability

Most relocation candidates fixate on one visa class (typically Skilled Worker via single sponsoring employer) and miss the parallel options (Talent, Self-employed, Family-class, retirement-track) that may have higher exit liquidity. The probability of landing a robust expat work-stack on first attempt with single-pathway thinking is perhaps thirty percent; with multi-pathway awareness it doubles or triples for the same candidate profile.

4 · What works

What works: (1) opening destination-country banking before relocation, not after — most banking systems are friendlier to non-residents than to newly-arrived residents; (2) picking the visa class by exit-liquidity not entry-speed — fast-entry visas (Digital Nomad) often lack permanent-residence pathway; (3) checking tax-residency treaty rules in the year of relocation, not assuming standard 183-day test; (4) consulting one registered immigration practitioner before submitting; (5) maintaining home-country tax compliance for at least two years post-relocation to keep that pathway open.

5 · What doesn't work

What does not work: (1) committing to one visa class with no fallback; (2) assuming destination tax-residency starts on arrival — actual rules are treaty-specific and complex; (3) closing home-country bank accounts pre-relocation — many destinations require parent-country financial trail to open local accounts; (4) underestimating biz-formation lead times for self-employed paths — six to nine months is normal in most OECD destinations; (5) ignoring spousal work-rights — some visa classes carry, some do not.

6 · Common pitfall

The biggest trap at TRAV work stage is assuming destination tax-residency starts on arrival. Actual rules are treaty-specific and complex, often spanning the relocation year across two regimes. Candidates who do not consult a destination-country tax practitioner before relocating commonly pay double-residency taxes in year one, sometimes paying twenty to thirty percent more total tax than necessary.

7 · Counter-intuitive insight

Counter-intuitively, the visa class with the longest application timeline is often the one with the highest exit-liquidity. Skilled Worker visas via sponsoring employer take six to twelve months but lead to settlement and naturalisation; Digital Nomad visas admit in 30-60 days but lack permanent-residence pathway. Optimise for exit-liquidity over entry-speed unless explicit short-stay intent applies.

8 · Highest-leverage move

The single highest-leverage move at TRAV work stage is to consult one registered immigration practitioner for a one-hour structured review before submitting any visa application. The cost (typically USD 200-500) is recouped many times over by avoiding documentation errors that cause the bulk of rejections.

Eight user intents

9 · Who gains most

Expat-bound professionals, founders contemplating moves, freelancers relocating to tax-friendly bases, dependents researching work-rights side of partner relocations, HR/relocation-mobility teams handling employee transfers.

10 · Irreducible essence

The irreducible essence: open destination banking before relocation; pick visa class by exit-liquidity; check tax-residency treaty rules early; consult registered practitioner once.

11 · Optimal timing

Six to twelve months before relocation. Visa programmes have lead times from one month to twelve months; tax-residency optimisation should ideally be planned six months pre-move.

12 · Where it matters most

26 cities have full work-stack profiles; 200-plus visa programmes catalogued. The 26 cities span all major OECD destinations plus emerging GCC and ASEAN tier-one hubs.

13 · Why misunderstood

Work stage on TRAV is misunderstood because candidates fixate on visa-class-as-binary (admitted or not) rather than visa-class-as-multidimensional (entry speed, settlement track, dependent rights, work scope, tax basis, exit liquidity). The multidimensionality matters across the relocation lifecycle.

14 · Highest-leverage sub-paths

Highest-leverage visa-class clusters vary. For tech-skilled: UK Skilled Worker + Singapore Tech.Pass + Canada Express Entry. For founders: UK Innovator Founder + UAE Golden Visa + Estonia e-Residency. For investors: Portugal Golden Visa post-2024 + Greece Golden Visa + Caribbean CBI programmes.

15 · Whose advice to trust

Trust: destination immigration ministries, OECD Model Tax Convention + actual bilateral treaty texts, registered immigration practitioners, national-banking regulators on foreigner banking access. Ignore: relocation-marketing companies promising outcomes, blog-post visa tips without legal grounding, single-anecdote success stories.

16 · How to proceed differently

Proceed with a relocation-pipeline tracker keyed by destination country: visa class, lead time, documentary status, financial requirements, banking pre-arrangement, tax-residency-year plan, dependent status. Review monthly.

Developer POV — for the architect, maintainer, AI tool, future contributor

Eight dev dimensions

17 · Data architecture

TRAV work stage composes from data/static/visa-programmes.php (200+ programmes), the 26 anchor-cities work-stack registry (full work + tax + banking + infrastructure profiles), and tax-residency-treaties.php (OECD treaty-text excerpts). Anchor-cities are a curated subset where TRAV has full work-stack profile depth.

18 · Schema markup

Same GovernmentService schema on per-visa pages as MAIN work stage. Place + WorkPlace + Organization schema on anchor-city profiles. The TRAV work stage shares the visa-programmes registry with MAIN work stage — single source of truth.

19 · Internal linking

Forward to cost/infra/decide. Outward to /work/{city}/, /visa/{country}/, /tax-residency/{country}/. Sister-rail to MAIN /toolkit/ (founder-readiness, trade-finance, etc.). Cross-content injector tokens: "expat", "tax-residency", "banking", "skilled-worker".

20 · Page-speed posture

Work stage on TRAV slightly lighter than MAIN work stage (5 visa-class clusters × 26 anchor-cities, vs MAIN 197 countries). Payload ~11 KB. Render ~200-360 ms.

21 · Mobile UX

Same responsive pattern. Visa-cluster cards 5-col → 2-col → 1-col.

22 · Accessibility

Same patterns. Cluster headings <h3>. Cards <a>. Heading hierarchy. Contrast AAA/AA.

23 · SEO saturation

Per-anchor-city work pages: /work/{city}/. Per-tax-residency: /tax-residency/{country}/. Sitemap: /sitemap-work-trav.xml + /sitemap-tax-residency.xml. Canonical + OG per page.

24 · Extensibility

New anchor-city: append to anchor-cities-work-stack.php with required fields (city, country, visa_options[], banking_setup, tax_basis, work_culture_notes). Stage auto-picks up.

Eight dev intents

25 · Who maintains

Joint. Anchor-cities curated set (26 cities). Updated semi-annually as relocation patterns shift.

26 · What tech stack

Tech: PHP arrays, helpers ajg_anchor_cities(), ajg_anchor_city_visa_options(). Front-controller routes: /work/, /work/{city}/, /tax-residency/, /tax-residency/{country}/.

27 · When to refresh

Semi-annual review for anchor-city set. Tax-residency data updated as treaties revise (typically 1-3 changes per year across OECD).

28 · Where in codebase

Code: data/anchor-cities-work-stack.php, data/tax-residency-treaties.php, /work/index.php, /work/city.php, /tax-residency/index.php, /tax-residency/country.php, includes/ajg-work-stack.php.

29 · Why this approach

Why a curated 26-anchor-city subset rather than full 2,326-city work-stack: depth-vs-breadth trade-off. 26 cities get full handwritten work-stack treatment (tax + banking + visa cross-product) which would be 2,326 × 4 fields = 9,300+ paragraphs to do at full coverage. Pareto: 26 cities cover 80%+ of expat-relocator interest.

30 · Which dependencies

Critical: anchor-cities-work-stack, visa-programmes (shared with MAIN), tax-residency-treaties. Optional: per-anchor-city PDF tax-summary overlays.

31 · Whose responsibility

Same ownership. Tax-residency data verified against OECD Model Tax Convention + actual bilateral treaties (linked from /tax-residency/{country}/ pages).

32 · How to extend

Promote a city from base 2,326-city set to anchor-city: append entry to anchor-cities-work-stack.php with full work-stack profile fields. Existing /cities/{slug}/ page gets enhanced layer at /work/{city}/.

Stage 3 · What it actually costs

Cost — where your salary actually goes furthest

The cost-of-living delta between high-income cities (London, NYC, Singapore) and arbitrage destinations (Lisbon, Mexico City, Bengaluru) is between 2× and 5× — but the variability inside each city is also enormous. A "Lisbon at $3K/month" lifestyle is genuinely possible, but only if you avoid the central districts that have absorbed most of the post-2020 nomad influx. The cost layer covers both medians and the practical cost of "the lifestyle you actually want", which are usually quite different.

Real estate is even more variable, and the rent vs buy decision now depends on visa-residency interactions that didn't matter pre-2020. Run the numbers properly, and ideally before you sign any 12-month lease.

2,596cities priced
34real-estate cities
15cost categories
USD/EUR/INR3 currencies
Q1-2026last refresh
Monthlyrefresh cycle

Eight ways into Cost

The Cost stage runs from /cost-of-living/ + /real-estate/ + /comparator/. 50 cities deep, 2,326 at index level. The ATLAS-1.3 living-cost-arbitrage map (live in the toolkit) is the formal version of the principal-flavoured cost lens.

who

Who is this stage for?

Relocation budgeters comparing cities head-to-head, salary-arbitrage seekers (people considering accepting a lower nominal salary in a lower-cost city), retirement planners optimising fixed-income lifestyle, and corporate mobility teams setting expat compensation.

what

What does it cover?

Cost-of-living index (50 cities deep, 2,326 at index level), real-estate prices (rent + purchase), cost comparator (city-pair head-to-head), local salary deciles (where available), tax burden including bilateral-treaty relief, plus the principal's preferred lens: salary-purchasing-power preserved across cities.

when

When should it be used?

As soon as a shortlist of cities has emerged from the Live stage. Cost is the stage where shortlists collapse — typically a 10-city Live shortlist becomes a 3-city Cost shortlist. Best applied with concrete monthly-budget assumptions rather than vague "reasonable" expectations.

where

Where does coverage extend?

Fifty cities deeply (with full cost-of-living + real-estate breakdown), 2,326 cities at index level (overall cost index, rent index, restaurant index, groceries index). Coverage densest for OECD destinations and Indian-context cities.

why

Why is salary arbitrage measurable?

Because cost-of-living is the most numerically tractable relocation lever. A USD 100,000 nominal salary preserves USD 78,000 of purchasing power in London but USD 195,000 in Mexico City — that's a 2.5× swing on the same gross-pay. Of all the comparison axes, cost is the one with the cleanest numerical answer.

which

Which sub-indices anchor the stage?

Rent (centre vs. periphery), groceries (basket of staples), restaurants (mid-range three-course meal), transport (monthly pass), utilities (apartment monthly), healthcare (insurance premium for expat), internet (monthly), schooling (international school tuition annual), leisure (gym + cinema + dining out per month), childcare (where applicable).

whose

Whose framework underwrites it?

Numbeo (crowd-sourced — wide coverage, moderate accuracy), Mercer Cost-of-Living Index (corporate dataset — narrow coverage, high accuracy for expat-tier), Expatistan (consumer cross-check), national statistical services (CPI, housing-index), local rent-platforms (ImmobilienScout, Rightmove, IDealista, NoBroker for Indian-context).

how

How does the stage connect downstream?

The cost comparator output feeds the Infra stage (does the budget include adequate safety/healthcare margin?) and the Decide stage (city comparator final). Upstream it cross-links to the main-site Jobs stage (does the offer cover the lifestyle?) and the College stage (does the family budget actually support that overseas tuition?).

Main-site counterpart

Cost decisions on the Travelogue feed directly into employer negotiations on the main site. The Jobs and Work stages on AJG are where the Cost output produces a counter-offer.

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV

User POV — for the relocator, founder, student, professional

Eight dimensions

1 · Possibility

In principle, a high-skill remote worker can preserve up to 2.5× nominal salary purchasing power by relocating from a high-cost OECD anchor (London, San Francisco, Sydney) to a tier-2 OECD or strong-currency emerging-market hub (Lisbon, Tallinn, Mexico City, Bengaluru, Tbilisi). The cost-of-living arbitrage is one of the largest single-decision financial improvements available to professional workers. The outer envelope on USD 100k nominal: roughly USD 78k purchasing power preserved in London; roughly USD 195k preserved in Mexico City. The arbitrage is real and measurable.

2 · Plausibility

Realistically, the cost-arbitrage opportunity preserves between 1.4× and 2× nominal-salary purchasing power for most cross-OECD relocations, with the largest gains for moves OECD→emerging-market and the smallest for tier-1 to tier-1 OECD swaps. The plausibility envelope assumes the relocator captures perhaps eighty percent of the headline arbitrage after relocation friction (housing setup, banking, healthcare paperwork), not the full headline number.

3 · Probability

Most relocation candidates either understate the arbitrage (anchor on home-city cost expectations) or overstate it (use Numbeo headline numbers without correcting for expat-tier housing premium). The probability of capturing the arbitrage at greater than 1.4× depends on (a) actually relocating rather than just considering, and (b) compressing relocation friction-cost below twenty percent of year-one savings. Most candidates fail at one or both.

4 · What works

What works: (1) running the cost comparator with concrete monthly-budget categories not headline indices; (2) accepting that expat-tier housing carries a thirty-to-fifty percent premium over local-resident housing in most cities; (3) capturing the arbitrage through full-year residency, not three-month visits — short stays carry tourist-tier pricing; (4) shifting fixed costs (subscriptions, accounts) to destination-country pricing as soon as possible; (5) maintaining a rough monthly burn-tracker for the first six months to validate the arbitrage was actually captured.

5 · What doesn't work

What does not work: (1) using single-source cost-of-living indices without cross-checking; (2) underestimating one-time relocation costs (visa fees, shipping, deposit, agency commission); (3) maintaining home-country fixed costs (rented apartment, gym membership) that cancel the arbitrage; (4) overconsuming on the cost-arbitrage gain — many relocators upgrade lifestyle so much they spend the saving; (5) ignoring currency-volatility risk — emerging-market arbitrage is real but currency-sensitive.

6 · Common pitfall

The biggest trap at cost stage is using single-source cost-of-living indices (typically Numbeo) without cross-checking. Numbeo is crowd-sourced and broad but underweights expat-tier housing and overweights local-resident housing. Cross-checking against Mercer plus actual local rent platforms produces a more accurate picture, often 25-40 percent higher than Numbeo alone suggests.

7 · Counter-intuitive insight

Counter-intuitively, the cost-arbitrage opportunity is largest in cities with strong local currencies versus the candidate home currency, not in cities with weak currencies. A USD-earning candidate moving to a USD-pegged-emerging-market city captures the arbitrage stably; moving to a weak-currency emerging-market city captures it volatilely. Stability matters as much as level.

8 · Highest-leverage move

The single highest-leverage move at cost stage is to compute a candidate-specific monthly burn-tracker for the destination city BEFORE relocating, then validate it during the first three months of residence. Most candidates eyeball the cost-arbitrage based on headline indices; the calibrated burn-tracker reveals whether the arbitrage was actually captured or eroded by upgrade-spending.

Eight user intents

9 · Who gains most

Relocation budgeters comparing cities head-to-head, salary-arbitrage seekers (people considering accepting lower nominal salary in lower-cost city), retirement planners optimising fixed-income lifestyle, corporate mobility teams setting expat compensation.

10 · Irreducible essence

The irreducible essence: cross-check at least two cost-of-living sources; compute candidate-specific burn-tracker; account for one-time relocation friction-costs; validate arbitrage during first three months.

11 · Optimal timing

As soon as a Live-stage shortlist has emerged. Cost stage is the convergence stage where 10-city shortlists collapse to 2-3 city decision pools. Best applied with concrete monthly-budget assumptions.

12 · Where it matters most

50 cities deeply covered (full cost-of-living + real-estate breakdown), 2,326 cities at index level. Coverage densest for OECD destinations and Indian-context cities.

13 · Why misunderstood

Cost stage is misunderstood because the comparison feels purely numerical but is actually behavioural. Two candidates with identical destination-burn-trackers can have radically different real costs based on lifestyle-upgrade discipline post-arrival.

14 · Highest-leverage sub-paths

Highest-leverage cost-arbitrage destinations for OECD-currency-earning candidates: Lisbon (1.4x preserved purchasing power), Mexico City (2x), Bengaluru (2.5x for Indian-context returning), Tbilisi (1.8x), Tallinn (1.3x). For weak-currency-earning candidates the arbitrage is reversed.

15 · Whose advice to trust

Trust: Numbeo (broad coverage), Mercer (narrow but accurate for expat-tier), Expatistan (consumer cross-check), national CPI from statistical services, local rent platforms. Ignore: aggregator-driven cheapest cities lists without methodology, marketing-driven retirement-haven articles.

16 · How to proceed differently

Proceed by building the candidate-specific burn-tracker spreadsheet with categories: rent, groceries, transport, utilities, healthcare insurance, schooling, leisure, savings target. Compare against current city same-category spending. Validate during first three months.

Developer POV — for the architect, maintainer, AI tool, future contributor

Eight dev dimensions

17 · Data architecture

TRAV cost stage composes from cost-of-living.php (Numbeo + Mercer + Expatistan cross-checked indices for 250 cities deeply, 2,326 at index level), real-estate.php (rent + buy benchmarks for 50 deep cities), currency-volatility-data.php (5-year rolling for 80 currencies). Burn-tracker template: data/burn-tracker-template.php with categorical breakdown.

18 · Schema markup

Dataset schema on cost-comparison pages; ProductCategory + Service schema on cost-component pages (rent, transport, healthcare). Per-city cost pages emit Dataset with cost-component breakdown as variableMeasured array.

19 · Internal linking

Forward to infra/decide. Outward to /cost/{city}/, /cost-comparison/{city-a}-vs-{city-b}/, /toolkit/living-cost-arbitrage/. Cross-content injector tokens: "cost", "rent", "salary-arbitrage", "purchasing-power", "currency".

20 · Page-speed posture

Cost stage payload ~12 KB. Compare-card grid + cost-component breakdown. Render ~220-380 ms. Cost-comparison pages slightly heavier (~14 KB) due to dual-city render.

21 · Mobile UX

Compare-cards 3-col → 1-col responsive. Cost-component bars use CSS-only progress-bar pattern (no JS). Tap-targets ≥48px.

22 · Accessibility

Cost-component bars use semantic <progress> elements with explicit aria-valuemin/max/now. Heading hierarchy. Cards <a>.

23 · SEO saturation

Per-city: /cost/{city}/. Pairwise comparison: /cost-comparison/{city-a}-vs-{city-b}/. Up to 250 × 249 = 62,250 pairwise URLs (curated subset of meaningful comparisons emitted, not full cross-product). Sitemap: /sitemap-cost.xml + /sitemap-cost-comparison.xml. Schema Dataset.

24 · Extensibility

New city cost data: append to cost-of-living.php with required fields (city, indices, cost_components[], data_source, last_updated). Stage card grid auto-picks up.

Eight dev intents

25 · Who maintains

Joint. Cost data refreshed quarterly (data sources update on different cadences; quarterly is the joint lowest-common-multiple).

26 · What tech stack

Tech: PHP arrays, helpers ajg_cost_of_living_all(), ajg_cost_compare(). Front-controller routes: /cost/, /cost/{city}/, /cost-comparison/, /cost-comparison/{a}-vs-{b}/.

27 · When to refresh

Quarterly refresh. Cron coordinates with master-refresh. IndexNow on edit.

28 · Where in codebase

Code: data/cost-of-living.php, data/real-estate.php, data/currency-volatility-data.php, /cost/index.php, /cost/city.php, /cost-comparison/index.php, /cost-comparison/pair.php, includes/ajg-cost.php.

29 · Why this approach

Why curated pairwise URLs rather than full cross-product: 250 × 249 = 62,250 raw pairs but only ~5,000 are meaningful comparison patterns (e.g. London vs NYC, Bangalore vs Mumbai, Lisbon vs Porto). Curated subset emitted at sitemap time; arbitrary pair URLs return canonical comparison structure but are flagged noindex if not in curated set.

30 · Which dependencies

Critical: cost-of-living.php, real-estate.php, currency-volatility-data.php. Optional: per-city historical-cost time-series, per-city demographic-overlays.

31 · Whose responsibility

Same ownership. Cost data verified against Numbeo + Mercer + Expatistan cross-source. Currency data via central-bank reference rates (no FX API at runtime — daily-cached snapshots).

32 · How to extend

New comparison pair: usually no manual addition — auto-emitted when both cities have cost data. To force-include a niche comparison: append slug-pair to data/cost-comparison-curated.php.

Stage 4 · The dailiness

Infrastructure — what makes a place liveable long-term

Most relocations don't fail on visa or cost — they fail on dailiness. The third winter in a sunless climate, the fourth time a delivery driver gets your address wrong, the moment you realise your local pharmacy doesn't carry the medication you actually need. The infrastructure layer covers the practical fabric: safety, climate, food culture, healthcare access, internet reliability, public transport, walkability, and the ineffable quality of "is this place actually pleasant to live in".

These are the things you only learn after 6-12 months in residence — but the data here lets you front-load some of that learning. Choose your dealbreakers before the move, not after.

Safety1 lens
Climate1 lens
Food1 lens
Connectivity1 lens
Transport1 lens
Healthcare1 lens

Eight ways into Infra

The Infra stage runs from /safety/ + /climate/ + /food/ + /connectivity/. Per-city infrastructure factsheets fire off the same lens-stack as the Live stage but with deeper drilldown into safety/climate/connectivity. Schema: BreadcrumbList, Place, Article, Dataset.

who

Who is this stage for?

Long-stay relocators (one year-plus), families with children, security-sensitive professionals, climate-vulnerable health profiles, cuisine-particular movers, remote-work-dependent professionals. Anyone whose stay-duration exceeds the cost-arbitrage horizon.

what

What does it cover?

Safety profile (crime stats + INFORM risk + WHO health-emergency), climate profile (annual averages + extremes + air quality + climate-change projections), food culture (dietary feasibility for vegetarian/vegan/halal/kosher/local-only), connectivity (broadband speed + mobile coverage + grid reliability + remote-work viability).

when

When should it be used?

After cost-shortlisting (Cost stage) and before final commitment (Decide stage). Infrastructure is the stage where cities that look attractive on the cost lens fall away — high-rent low-cost-of-living cities sometimes hide poor air quality, high crime, or unreliable healthcare.

where

Where does coverage extend?

Per-city infrastructure factsheets for the 2,326-city corpus at varying depth. OECD destinations and India-context cities are densest; emerging-market secondary cities are at lighter base coverage but still factsheet-complete.

why

Why does cost fall away?

Because cost equilibrates within months but infrastructure determines whether you stay. A six-month relocation can tolerate weak healthcare; a five-year relocation cannot. A cost-arbitrage city with poor air quality (PM2.5 above 40 μg/m³ annualised) is a dealbreaker for asthmatic family members regardless of how favourable the rent looks.

which

Which sub-indices anchor the stage?

Crime rate (homicide per 100k + property crime per 100k), INFORM risk index (humanitarian crisis + conflict + natural-disaster), WHO Air Quality (PM2.5 + PM10 + NO2 + O3), broadband speed (Speedtest median + median-50th), grid-reliability (power outages per year + duration), drinking-water safety, healthcare access (doctors per 1,000 + hospital beds + insurance availability for expats).

whose

Whose framework underwrites it?

WHO (air quality, health), UN (INFORM Index for risk, UNICEF for child-welfare), national statistical services (crime, healthcare access), Speedtest (broadband), Numbeo (crowd-sourced perception of safety), AccuWeather + national meteorological services (climate), AJG editorial cross-checks for current state.

how

How does the stage connect downstream?

Per-city infrastructure factsheet links forward to the Decide stage (final comparator + listicle), and upstream cross-links to the main-site School stage (schooling-availability lens), Work stage (healthcare-insurance lens for expat workers), and Business stage (operational continuity lens for founders).

Main-site counterpart

Infrastructure for residence cross-applies to infrastructure for schooling and work. The College and Work stages on the main site reference Travelogue Infra for institutional and operational placement decisions.

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV

User POV — for the relocator, founder, student, professional

Eight dimensions

1 · Possibility

In principle, every relocator can pre-validate the infrastructure quality of any candidate destination — air quality (WHO PM2.5 + PM10), safety (homicide + INFORM risk), connectivity (broadband speed + grid reliability), healthcare (doctors per 1,000 + insurance availability for expats), water + food safety. The outer envelope of pre-relocation infrastructure due diligence is broader than most relocators realise; the data exists, the AJG factsheet aggregates it.

2 · Plausibility

Realistically, infrastructure quality varies enormously across the 2,326-city corpus and a deliberate relocator can identify dealbreakers before commitment. A family with an asthmatic member should know the destination annual PM2.5 reading; a remote worker should know broadband-stability median; a long-stay relocator should know healthcare-insurance availability for expats and the typical out-of-pocket medical-emergency cost. The plausibility envelope is well-defined: this stage filters cities that fail dealbreakers.

3 · Probability

Most relocators underweight infrastructure relative to cost and visa. They optimise on the first two and discover infrastructure problems after relocating. The probability of relocation-disappointment correlates more strongly with infrastructure-mismatch than with cost-mismatch or visa-mismatch — because cost adjusts and visa is binary, but infrastructure is the operating environment for every day post-relocation. The probability of post-relocation regret falls sharply for relocators who weighted infrastructure during selection.

4 · What works

What works: (1) treating infrastructure as a hard-filter rather than soft-preference — air quality dealbreakers should eliminate, not de-rank; (2) checking destination healthcare-insurance availability for expats before relocation, not on arrival; (3) talking to two existing expats about the actual lived experience of safety, connectivity, and healthcare; (4) test-staying for at least one month during the worst season (monsoon, winter, summer-extreme) before commitment; (5) maintaining home-country emergency-medical insurance bridge for the first six months.

5 · What doesn't work

What does not work: (1) optimising on cost or visa while ignoring infrastructure; (2) trusting headline air-quality numbers without checking seasonal variation (Delhi PM2.5 monthly varies by 4× between best and worst months); (3) assuming OECD-tier healthcare quality in non-OECD destinations; (4) ignoring grid-reliability for remote workers — power outages compound over months; (5) underestimating the infrastructure friction of life-administration paperwork (banking, healthcare, schooling) in low-bureaucratic-quality destinations.

6 · Common pitfall

The biggest trap at infra stage is treating air-quality, safety, and connectivity numbers as static when they are actually highly seasonal. Delhi PM2.5 varies by 4x between best and worst months; Bangkok flood risk is binary by season; Bengaluru power-cut frequency triples in monsoon. Annual averages mask the worst-case experience that the candidate will actually have.

7 · Counter-intuitive insight

Counter-intuitively, healthcare infrastructure quality matters less than healthcare-insurance-availability for expats. Candidates who fixate on hospital quality miss that as foreigners they may not be able to access top hospitals without expensive expat-tier insurance. The accessible healthcare quality is what matters; the theoretical healthcare quality often does not.

8 · Highest-leverage move

The single highest-leverage move at infra stage is to spend one full month in the candidate city during the worst-infrastructure season — monsoon, winter, summer-extreme, election season for politically-volatile destinations. The lived experience of bad infrastructure during peak stress is the dealbreaker test; if the candidate can tolerate the worst, average is comfortable.

Eight user intents

9 · Who gains most

Long-stay relocators (1+ years), families with children (school + healthcare critical), security-sensitive professionals, climate-vulnerable health profiles, cuisine-particular movers, remote-work-dependent professionals (connectivity critical).

10 · Irreducible essence

The irreducible essence: treat infrastructure as hard-filter not soft-preference; seasonal variation matters more than annual averages; expat-accessible quality matters more than theoretical quality.

11 · Optimal timing

After cost-shortlisting and before final commitment. Infrastructure is the stage where attractive cities on the cost lens fall away. Best applied during one-month worst-season test-stay.

12 · Where it matters most

Per-city infrastructure factsheets cover the 2,326-city corpus at varying depth. OECD destinations and India-context cities densest. Emerging-market secondary cities at lighter base.

13 · Why misunderstood

Infra is misunderstood because cost adjusts within months but infrastructure determines whether candidates stay. Six-month relocations can tolerate weak healthcare; five-year relocations cannot. A cost-arbitrage city with PM2.5 above 40 µg/m³ annualised is a structural dealbreaker for asthmatic family members regardless of rent.

14 · Highest-leverage sub-paths

Highest-leverage infrastructure dimensions vary by profile. For families: schooling availability + healthcare quality + safety. For remote workers: broadband stability + grid reliability + time-zone alignment. For health-sensitive: air quality + healthcare access + medical-emergency cost.

15 · Whose advice to trust

Trust: WHO (air quality + health), UN INFORM Index (humanitarian risk + conflict + natural disaster), Speedtest (broadband), national statistical services (crime, healthcare access), local-resident conversations. Ignore: tourism-board promotional material, single-incident sensational news coverage, retiree forums dominated by selection-biased responses.

16 · How to proceed differently

Proceed by listing the top three dealbreaker infrastructure dimensions for the candidate profile, then filtering the cost-stage shortlist against those three. Cities that fail any of the three dealbreakers are eliminated regardless of cost-arbitrage. Test-stay during worst-season validates the survivors.

Developer POV — for the architect, maintainer, AI tool, future contributor

Eight dev dimensions

17 · Data architecture

TRAV infra stage composes from infra-quality.php (per-city: WHO PM2.5/PM10, Speedtest broadband, INFORM safety risk, healthcare-doctors-per-1000, water-quality, grid-reliability), seasonal-variance.php (monthly variation for climate-sensitive metrics), expat-healthcare-access.php (per-country expat-tier insurance availability + cost). 250 cities deep; 2,326 at index level.

18 · Schema markup

Per-city infra pages: Place + DigitalDocument schema for the factsheet. Per-metric pages (e.g. /infra/air-quality/{city}/): Dataset schema. The seasonal-variance data emits as Dataset.variableMeasured array.

19 · Internal linking

Forward to decide. Outward to /infra/{city}/, /infra/{metric}/{city}/, /healthcare/{country}/, /broadband/{city}/. Cross-content injector tokens: "infrastructure", "air-quality", "healthcare", "broadband", "safety".

20 · Page-speed posture

Infra stage payload ~12 KB. Per-city infra pages ~14-16 KB (multiple metrics rendered). Render time ~220-400 ms. Seasonal-variance charts use SVG (10-chart-types via includes/ajg-viz.php) — no JS chart library.

21 · Mobile UX

Metric cards 4-col → 2-col → 1-col. Seasonal-variance SVG charts max-width 100% for responsive. Tap-targets ≥48px.

22 · Accessibility

SVG charts have <desc> + <title> per chart. Color-blind-safe palettes for metric thresholds (red/yellow/green replaced with navy/silver/gold per strict palette). Heading hierarchy. Metric tables have <thead> + <th scope="col">.

23 · SEO saturation

Per-city: /infra/{city}/. Per-metric-per-city: /infra/{metric}/{city}/. Per-country healthcare: /healthcare/{country}/. Sitemap: /sitemap-infra.xml + /sitemap-healthcare.xml. Schema Dataset on metric pages.

24 · Extensibility

New metric: append to infra-quality.php with required fields (slug, label, unit, source, threshold_good, threshold_warn, threshold_bad). Renderer auto-picks up via ajg_infra_metric_render(). New metric type ship: ~30 minutes.

Eight dev intents

25 · Who maintains

Joint. Infra data refreshed quarterly (WHO air-quality annually, Speedtest monthly, INFORM monthly).

26 · What tech stack

Tech: PHP arrays per metric, helpers ajg_infra_quality_all(), ajg_infra_metric_render(), ajg_infra_seasonal_variance(). SVG chart generators in includes/ajg-viz.php (10 chart types).

27 · When to refresh

WHO PM2.5 annual; Speedtest monthly; INFORM monthly; healthcare-access semi-annual. Cron-coordinated. IndexNow on edit.

28 · Where in codebase

Code: data/infra-quality.php, data/seasonal-variance.php, data/expat-healthcare-access.php, /infra/index.php, /infra/city.php, /infra/metric.php, /healthcare/index.php, /healthcare/country.php, includes/ajg-infra.php, includes/ajg-viz.php.

29 · Why this approach

Why seasonal-variance as separate data file rather than embedded in main metric data: monthly granularity bloats the main metric file 12x; separate file keeps main file render-friendly while seasonal-variance is loaded only for chart generation.

30 · Which dependencies

Critical: infra-quality.php, seasonal-variance.php, expat-healthcare-access.php, ajg-infra.php helpers, ajg-viz.php SVG generators.

31 · Whose responsibility

Same ownership. Data sources: WHO Global Air Quality Database, Speedtest Global Index, UN INFORM Risk Index, OECD Health Statistics. Cross-validated for OECD destinations; emerging-market secondary cities use national-statistics-office data with explicit data_source citation.

32 · How to extend

New metric: append to infra-quality.php + register in ajg_infra_metrics_registry() helper + add CSS threshold colours. Renderer + sitemap auto-pick up. New metric ship: ~30 minutes including handwritten threshold-explanation prose for 250 cities (rendered at request, ~5 min compose per city).

Stage 5 · The commit point

Decide — comparators, listicles, decision trees

The hardest part of a relocation isn't the data. It's deciding. The decision layer is built around the scenarios real people actually face: "I have $5K/month remote income, I want to be in Asia or Europe, prioritise warm weather and good food, must have English-speaking healthcare." That's a decision-tree problem, not a dictionary lookup. The compound listicles answer exactly these multi-axis questions.

Cross-link to the trade nexus if your decision involves business formation, import-export, or anything that touches the multilateral trade layer — the sister site at allfrontierglobal.com runs 2,596 cities cross-product with 1,162,501+ data points, also free.

Eight ways into Decide

The Decide stage runs from /best/ + /listicles/ + /comparator/ + /library/tree/. Comparator output links the user back to the main-site Business stage where the location decision produces real-world consequences. The lineage from Live to Decide is closed and the loop to the main site is enforced.

who

Who is this stage for?

Ready-to-decide relocators with a 2-3 city shortlist, advisors helping clients pick between final candidates, corporate mobility teams committing to an assignment city, families converging on a single decision after navigating Live, Work, Cost, and Infra.

what

What does it cover?

Decision-support apparatus: 25 best-of city lists, 582 compound listicles (axis-pair filtered city sets), 140-node decision tree for relocation, head-to-head city comparator across all 15 lenses, plus 12 React AI artifacts as decision aids. The Decide stage closes the loop from Live to commitment.

when

When should it be used?

When a shortlist has converged to two or three cities and the decision needs scaffolding rather than data. Earlier stages produce information; Decide produces decision support. Used incorrectly (too early) it overwhelms; used correctly (after shortlisting) it accelerates.

where

Where does coverage extend?

All 2,326 cities are accessible through the comparator and listicle apparatus, but the decision-tree apparatus is concentrated on the 250 most relocation-relevant cities (OECD destinations, GCC, ASEAN tier-one, plus India-context). Best-of lists span every major decision axis: best for families, best for nomads, best for value, best for safety, best for climate.

why

Why does the decision need scaffolding?

Because the decision is multi-axis and the human brain cannot weight 15 lenses simultaneously without aid. Comparators reduce 15 lenses to head-to-head pairwise diff; listicles pre-filter by axis pairs; decision trees walk the user through deliberate sequence. The scaffolding is the value, not the data.

which

Which decision-support tools anchor the stage?

City comparator (15-lens head-to-head, up to 4 cities at once), 25 best-of lists (best for nomads, families, value, safety, etc.), 582 compound listicles (best low-tax cities with strong banking, etc.), 140-node decision tree (relocation choice walkthrough), 12 React AI artifacts (interactive decision aids).

whose

Whose framework underwrites it?

AJG editorial composition synthesising Live + Work + Cost + Infra outputs. The 12 React AI artifacts are AJG-built interactive components for specific decision contexts (climate-aware-cost-comparator, family-fit calculator, tax-residency optimiser, etc.).

how

How does the stage close the loop?

Decide is the terminal stage on the Travelogue. Its output cross-links back to the main-site Business stage (where the decision produces operational consequences for founders) and Work stage (where the decision drives visa-pathway commitment). The lineage is complete.

Main-site counterpart

Decide is the terminal stage on the Travelogue. Its sister stage on the main site is Business — where the location decision produces operational consequences and the lineage closes.

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV

User POV — for the relocator, founder, student, professional

Eight dimensions

1 · Possibility

In principle, a relocator with full Live + Work + Cost + Infra inputs has all the data needed to make a high-quality decision. The 25 best-of city lists, 582 compound listicles, head-to-head city comparator, 140-node decision tree, and 12 React AI artifacts provide more decision support than any individual relocator can absorb. The outer envelope of decision-support apparatus is wider than necessary; the constraint is the relocator's capacity to weight rather than the apparatus's capacity to inform.

2 · Plausibility

Realistically, the decision-support apparatus collapses a 10-city shortlist to a 2-3 city decision pool reliably, but cannot make the final commit-or-not decision. The plausibility envelope is: apparatus reduces uncertainty by perhaps eighty percent; the residual twenty percent is irreducible, value-laden, life-circumstance-specific. Acknowledging the irreducible uncertainty is itself a decision-support outcome.

3 · Probability

Most relocators either over-rely on the apparatus (waiting for certainty before committing) or under-rely on it (deciding on impulse without comparators). The probability of a high-quality relocation decision is highest for relocators who use the apparatus to converge to 2-3 cities, then test-stay rather than analyse further, then commit on first-month evidence. Pure analysis past the 2-3 city stage produces diminishing returns.

4 · What works

What works: (1) using comparators to converge a 10-city shortlist to 2-3 cities; (2) test-staying in each of the 2-3 cities for one month each before final commit; (3) committing on first-month lived evidence rather than continuing to analyse; (4) accepting that the residual uncertainty is irreducible and the decision must absorb it; (5) maintaining a six-month exit option for the chosen destination, allowing reversal without catastrophic loss.

5 · What doesn't work

What does not work: (1) waiting for certainty before committing — it never arrives; (2) deciding without test-staying; (3) over-weighting any single comparator output (the decision tree, the listicles, the comparator) when the others disagree; (4) committing to multi-year residency on first-week feelings; (5) closing all exit options on commitment — first-year reversibility is operationally cheap and decision-support immense.

6 · Common pitfall

The biggest trap at decide stage is waiting for analytical certainty before committing. The decision-support apparatus reduces uncertainty by perhaps eighty percent; the residual twenty percent is irreducible, value-laden, and life-circumstance-specific. Candidates who keep analysing past the 80-percent-certain threshold produce diminishing returns; the marginal hour past that point usually delays action without improving decision quality.

7 · Counter-intuitive insight

Counter-intuitively, the most reliable decision-support input is not the most data-rich one but the one-month test-stay in each finalist city. A month of lived experience produces more decision-relevant evidence than any quantity of factsheet review. Candidates who treat data as substitute for experience produce worse decisions than candidates who treat data as complement to experience.

8 · Highest-leverage move

The single highest-leverage move at decide stage is to commit to a 6-month exit option for the chosen destination, allowing reversal without catastrophic loss. First-year reversibility is operationally cheap (paid rent, return-flight, retained domestic banking) and decision-support immense — it removes the all-or-nothing pressure that causes most relocation deferrals.

Eight user intents

9 · Who gains most

Ready-to-decide relocators with a 2-3 city shortlist, advisors helping clients pick between final candidates, corporate mobility teams committing to assignment cities, families converging on a single decision after navigating Live, Work, Cost, Infra.

10 · Irreducible essence

The irreducible essence: collapse the 10-city shortlist via comparators, test-stay the 2-3 finalists, decide on first-month lived evidence, preserve a 6-month exit option.

11 · Optimal timing

When the shortlist has converged to 2-3 cities and the decision needs scaffolding rather than data. Earlier in the relocation process the apparatus overwhelms; later it accelerates. Used at the right stage it compresses weeks of indecision into days.

12 · Where it matters most

All 2,326 cities are accessible through comparator + listicle apparatus, but the decision-tree apparatus concentrates on the 250 most relocation-relevant cities (OECD destinations, GCC, ASEAN tier-one, Indian-context). Best-of lists span every major decision axis.

13 · Why misunderstood

Decide stage is misunderstood because candidates conflate decision support with decision making. The apparatus does not make the decision; it scaffolds the candidate own decision. The residual irreducibility is the candidate value structure, which no apparatus can compute.

14 · Highest-leverage sub-paths

Highest-leverage tools at this stage: city comparator (15-lens head-to-head), 25 best-of lists (axis-specific filtering), 582 compound listicles (cross-axis pre-filtering), 140-node decision tree (sequential walkthrough), 12 React AI artifacts (interactive decision aids). Use them in order: comparators first, listicles second, decision-tree third if needed.

15 · Whose advice to trust

Trust: AJG editorial composition synthesising all upstream stage outputs, current-resident conversations in finalist cities (LinkedIn or expat forums), one-month test-stay lived evidence. Ignore: aggregator best places to relocate lists without methodology, single-anecdote relocation stories, agency recommendations aligned with their commission structure.

16 · How to proceed differently

Proceed by collapsing the 10-city shortlist via comparator (1 hour), then via listicles for axis-pair filtering (1 hour), then via decision-tree walkthrough for residual ambiguity (1 hour). Test-stay each finalist for one month. Commit on first-month evidence with 6-month exit option preserved.

Developer POV — for the architect, maintainer, AI tool, future contributor

Eight dev dimensions

17 · Data architecture

TRAV decide stage composes from the apparatus: comparator-config.php (15 lenses), best-of-lists.php (25 curated lists), compound-listicles.php (582 cross-axis pre-filtered), decision-tree.php (140 nodes, 209 cross-links), react-artifacts-data.php (12 React AI artifact schemas). The decide stage is the convergence point — pulls from every prior stage data.

18 · Schema markup

CollectionPage schema on the apparatus index pages; SoftwareApplication schema on the React AI artifacts; ItemList on best-of and listicle pages. Decision-tree nodes emit Question + AnswerOption schema for the 140 decision nodes.

19 · Internal linking

Decide is the most cross-linked TRAV stage. Inward links from every prior TRAV stage. Outward to /comparator/, /best-of/{slug}/, /listicles/{slug}/, /decision-tree/{node}/, /artifacts/{slug}/. Cross-content injector dense on this stage.

20 · Page-speed posture

Decide stage payload ~13 KB on homepage. Comparator pages slightly heavier (~16 KB; renders 15-lens head-to-head). Best-of and listicle pages: ~12-15 KB. Decision-tree node pages: ~10 KB each. Render times: ~200-450 ms range.

21 · Mobile UX

Comparator collapses from side-by-side to stacked at narrow viewports. Best-of lists use ordered <ol>. Decision-tree shows next-node options as tap-targets ≥48px. React artifacts are responsive by design.

22 · Accessibility

Comparator: side-by-side rendering uses <table> with proper <thead>+<th scope=col>+<td> for screen-reader navigation. Decision-tree node options are <a> with descriptive text. React artifacts have keyboard nav + ARIA labels.

23 · SEO saturation

Comparator URLs: /comparator/{a}-vs-{b}/ (curated). Best-of: /best-of/{slug}/. Listicles: /listicles/{slug}/. Decision-tree: /decision-tree/{node-slug}/. React artifacts: /artifacts/{slug}/. Each canonical. Schema per page-type. IndexNow on edit. Sitemaps split by section.

24 · Extensibility

New comparator lens: append to comparator-config.php (current 15 lenses). New best-of list: append to best-of-lists.php. New listicle: append to compound-listicles.php. New decision-tree node: append to decision-tree.php with parent + children + content. New React artifact: add JS file + register in react-artifacts-data.php.

Eight dev intents

25 · Who maintains

Joint. Comparator config edited rarely (lenses stable). Best-of and listicles updated as travel-trends shift (typically monthly). Decision-tree node edits as user feedback arrives.

26 · What tech stack

Tech: PHP arrays for non-React content; React (vanilla, no framework dependency on live site beyond a single artifact-specific JS file per artifact). Helpers ajg_comparator_lenses(), ajg_best_of_all(), ajg_listicles_all(), ajg_decision_tree_node().

27 · When to refresh

Comparator config rare-edit. Best-of monthly. Listicles monthly. Decision-tree node-edits as feedback arrives. React artifacts: refresh on data dependency change.

28 · Where in codebase

Code: data/comparator-config.php, data/best-of-lists.php, data/compound-listicles.php, data/decision-tree.php, data/react-artifacts-data.php, /comparator/, /best-of/, /listicles/, /decision-tree/, /artifacts/, includes/ajg-comparator.php, includes/ajg-decision-tree.php.

29 · Why this approach

Why include React artifacts at all (breaks the no-JS-framework rule): explicitly scoped — artifacts are fully self-contained per-page, do not affect the rest of the site, and provide interactive decision support that cannot be reasonably done server-side (e.g. real-time slider-based cost-comparison). Each artifact is a single self-contained JS file, no build pipeline.

30 · Which dependencies

Critical: comparator-config, best-of-lists, compound-listicles, decision-tree, react-artifacts-data. Optional: per-artifact PDF export. Required for stage render: comparator-config + best-of-lists.

31 · Whose responsibility

Same ownership. Decision-tree node content is the most editorially intensive content on TRAV (140 hand-authored nodes, 209 cross-links between nodes); maintained jointly with version-tracked node-edit-history.

32 · How to extend

New decision-tree node: (1) decide where in the tree it slots; (2) write node content (typically 80-150 words); (3) register in decision-tree.php with parent_node + children_nodes; (4) update parent node to include the new child option; (5) re-run cross-link verification (admin/decision-tree-verify.php). Total ship: ~30 minutes per node.

Sister site · v139 cross-pollination

Five heroes on allfrontierglobal.com

Travelogue covers the lifestyle data — climate, cost, food, infrastructure. The trade-nexus sister site covers the rest of borderless life: studying, working, building skills, and finding jobs across countries. All five heroes below are free, deterministic, no API keys, and they cross-link back into Travelogue at every level.

📚 Study & research network — purposed.in + Uuka

Economics → Law → Political Science → Sociology → Anthropology → Geography → Urban Studies → ✍ Essay Generator →

Live data infrastructure

Factsheet entry · system telemetry

For users who want to drop straight into the data layer — counts, registries, sitemaps, and discoverable axes — without navigating the journey above.

2,596 cities 184 countries 15 intelligence lenses 1082 visa regimes 1,162,501 searchable units 40 live axes 23,665,457 live data points 34 real-estate cities 26 biz-formation cities 23 tax jurisdictions

Travelogue legacy · since v9.3

The Travelogue archive — viewed through the eight intents

The travelogue subdomain has been under continuous composition since v9.3, currently at v22.0 with 2,326 cities across 201 country keys and a ~5.3 million URL surface. Per SO #93, the archive itself is treated as an entity and surfaced through the eight-intent lens.

Who travels with it

Digital nomads at every stage (experimental, veteran), expat-relocating professionals, salaried remote workers negotiating their first move, freelance consultants choosing a tax-residency base, retired professionals planning second-act geographies, MSME founders scouting target markets in person. Eight personas overlap with the AllfrontierGlobal main-site fourteen, refracted through the travel rather than career lens.

What it covers

Five intelligence layers A–E (climate, cost, safety, infrastructure, food) plus layers F (real estate), G (visa/tax) and H (business/work). 32-angle compound listicle engine producing ~582 indexable URLs. Full JSON-LD suite: BreadcrumbList, Article, TouristDestination, Country, Dataset, TouristAttraction, WebPage. 11,837 PDFs indexed. 15-lens unique content generator producing 3 distinct paragraphs per city × lens combination.

When to use which surface

Pre-trip (visa + tax-residency math): use the visa and tax layers. Mid-trip (cost + safety + infrastructure): the live A–E layers. Post-trip (rooting decisions): the F (real estate) and G (residency) layers. Always: the desk for live updates.

Where the depth lies

The 2,326 cities are structured by 23 countries with full visa/tax depth (layer G), 26 cities with full business-and-work depth (layer H), 34 cities with real-estate depth (layer F), and the full set with the A–E baseline. Country-level coverage spans 201 country keys; the next expansion wave adds Pacific Island depth and African Sahel coverage.

Why this rather than the search-engine alternative

Generic travel content optimises for ad clicks and trip-bookings. The travelogue here optimises for decisions that compound — choosing a digital-nomad base for two years, choosing a target jurisdiction for relocation, choosing a tax-residency strategy for the next decade. The depth is operational rather than promotional.

Which lens fits your question

The 15-lens generator (climate, cost-of-living, safety, infrastructure, food, real estate, visa, tax, business friendliness, healthcare access, language, time zone, internet quality, expat density, weekend-trip range) gives every city a 15-paragraph lens stack. Pick a lens to filter; pick a city to dive deep.

Whose data underwrites it

Numbeo (cost), Global Peace Index (safety), Köppen (climate), Speedtest (infrastructure), TasteAtlas (food), local statistical agencies (real estate), national tax authorities (visa/tax), national chambers of commerce (business friendliness). 140 authority sources tracked in the desk. All cited via Schema.org `isBasedOn`.

How it composes

Same flat-file PHP 8.3 stack as the main site. Same unified chrome, same single-fire pixels, same strict palette, same WCAG discipline. Travelogue-specific helpers in includes/lens-unique-content.php and includes/cities-essentials.php. Function-declarations-only; no re-include allowed (per v45.1 dev learning).

Recently added · v140.5

What's new — paired with the trade-intel side

AJG operates two sister sites: this travel-intel side and the trade-intel companion at allfrontierglobal.com. The v140.5 ENRICH batch (SO #69) shipped 5 entity kinds × 9 entries × 10,232 handwritten words across the trade-intel side; first travelogue depth-2 wave (Lisbon, Bangalore, Mexico City as digital nomad case studies) is queued for v140.6. Coverage map: live coverage tree.

already authored

Connectivity (4 expat-living axes)

Visa pathways, banking access, healthcare access, infrastructure quality across 2,326 cities × 201 countries.

v140.6+ deepening

Digital Nomad Visa atlas

23+ DN visa countries with regulatory framework, eligibility, tax-residency implications. Authored deep-dives queued.

trade-intel sister · v140.3

Trade Connectivity Atlas →

8-axis trade connectivity: maritime chokepoints, air cargo hubs, submarine cables, payment rails, energy pipelines, trade documentation, multilateral overlays. 22,091 words.

ENRICH protocol (SO #69): homepage-first link-depth pass, top-to-bottom of both sites, all content types, handwritten max-density. Live coverage tree →

🗺 Learning Progress Map School → Undergraduate → Postgraduate → Professional
Open map →
🏫 School 🎓 Undergraduate 🔬 Postgraduate 💼 Professional Full decision tree ↗
PhiloJain Music
Loading…

Explore

Explore the AJG knowledge graph

Every page in the AJG platform cross-links to these primary entities. Click any pill to explore that branch of the knowledge graph.