# UAE v2 — Property Finder's UAE new projects on the Malaysia project page, priced against Bayut's buildings

> 📍 Part of the project catalogue doc set — the map and routing table is
> [start-here.md](/docs/modules_handbook/shared/project-catalogue/start-here.md). The SUBJECTS come from
> provider `propertyfinder-nl` ([propertyfinder-new-projects.md](/docs/modules_handbook/shared/project-catalogue/propertyfinder-new-projects.md)),
> the EVIDENCE from provider `bayut` ([bayut.md](/docs/modules_handbook/shared/project-catalogue/bayut.md));
> the design and prototype figures are in [uae-new-project-analysis-plan.md](/docs/planning/uae-new-project-analysis-plan.md).

## What it does

**Analyze Property → New Projects** gains a **UAE v2** tab beside the UAE one (`?country=ae-v2`). It
lists the UAE new projects **Property Finder** feeds (owner, 2026-10-09: Property Finder is the UAE
new-project reference; Bayut is the subsale reference only), and each card opens the **Malaysia**
project page — the same tabs and the same analysis a member gets on a Malaysian launch:

| Malaysia page piece | What a UAE v2 project shows |
|---|---|
| Units · Price | The developer's **unit types from Property Finder** — one layout per bedroom group (per building, per property type) that has **a price and a size** (the owner's rule as settled 2026-10-09; the data set fills gaps from the project's own recent sales), priced and sized from its `display` figures, with its drawings — where it has any — copied to our storage. A type without a price or a size is not listed at all |
| Investment Analysis → Market Value | Median PSF of nearby Bayut buildings' **DLD sales, last 12 months**, nearest within 1 km (2 km fallback); verdict ±15 % |
| Investment Analysis → Rental | **Ejari rent contracts, last 12 months**, in ready buildings within 1–2 km, filtered to the layout's bedrooms → rent PSF × size. A new community often has no ready building within 1 km (Nautis Residences: nearest 1.02 km), so the Whole Unit tab opens on the 2 km ring and says so (2026-10-10) |
| Summary / Financial Projection | Same maths, in AED |
| Analyze Property → Layout Analysis | The **UAE tab** (`?country=ae`, 2026-10-11): one row per v2 layout in AED, read from this deployment's own `layout_analyses` rows (`BuildLayoutTable::sourceFor()`), AED price bands, no Malaysian maintenance in the cash flow. Filled by `layouts:project --country=AE --state=Dubai --run` on wk — see [main/analyze-property/readMe.md](/docs/modules_handbook/main/analyze-property/readMe.md) *Layout Analysis* |

The project is pinned where the Property Finder ⇄ Bayut match put it (`location_used`: the matched
Bayut building for 2,228 of 2,990, else Property Finder's own community-level pin), so "nearby" is
measured from the building, not the community. Before 2026-10-09 the subjects were Bayut's own new
projects; they were retired because their locations were not accurate enough (runbook rule 7).

Prices are **AED** throughout. Where a figure needs data we do not have, the page prints **`-`**
instead of a Malaysian assumption: the entry cost (MY stamp duty + legal), the maintenance /
service charge, the BMS convenience score (MY's amenity feed), a building's completion year.

The tab and its projects are **portal-only and unpublished** — the public site, sitemap and SEO never
list them.

## How it works

### One rule, asked in three places

> **Since 2026-10-14 the rule is one TABLE, per country:** `CatalogueDetailService::PORTAL_LAUNCH_PROVIDERS`
> (`AE` → `propertyfinder-nl`, `SG` → `edgeprop-sg`), read through `portalLaunchProvider()`,
> `rendersAsPortalLaunch()`, `memberMaySeePortalLaunch()` and `BuildNewProjectListing::portalLaunchScope()`.
> `rendersAsUaeV2()`, `memberMaySeeUaeV2()` and `uaeV2Scope()` are the UAE's wrappers over them and keep
> the UAE's one exclusion (a row the older `propertyfinder` feed carries stays on its old page). Singapore's
> launches use the same route on their own country tab — see
> [singapore.md](/docs/modules_handbook/shared/project-catalogue/singapore.md) §4.


`CatalogueDetailService::rendersAsUaeV2(CatalogProject)` — a UAE project with an **active
`propertyfinder-nl` source (`CatalogueDetailService::UAE_V2_PROVIDER`) and no active `propertyfinder`
source**, while `project_catalogue.uae_v2.enabled` (`UAE_V2_ENABLED`, default on). A project the OLDER
PropertyFinder feed also carries keeps the page it already had. A Bayut-only row is never v2: since
2026-10-09 Bayut rows are subsale buildings, evidence rather than subjects. The listing, the card
builder and the controller all read the constant, never the provider code.

- **The listing** — `BuildNewProjectListing::execute(..., provider: CatalogueDetailService::UAE_V2_PROVIDER)`
  swaps `publiclyListed()` for `BuildNewProjectListing::uaeV2Scope()`, the SQL twin of the rule.
  `AnalyzePropertyController::newProjects()` maps `?country=ae-v2` to it; the tab exists only when the
  UAE is a market of the hostname (Setting → Markets). **Since 2026-10-10 the portal shows ONE UAE tab**
  (owner: "hide the old UAE tab"): with `project_catalogue.uae_v2.replaces_legacy_tab` on (the default,
  `UAE_V2_REPLACES_LEGACY_TAB`), the v2 tab wears the country's name, the older feed's `ae` tab is
  dropped from the portal's tab row, and `?country=ae` in the portal serves the v2 list too. The
  public `/ae/new-projects` lists only PUBLISHED projects, and v2 projects are unpublished and
  members-only — so since the older feed was deleted from the master (2026-10-15,
  [uae-v2-hub-import.md](/docs/modules_handbook/shared/project-catalogue/uae-v2-hub-import.md)) that
  public page lists nothing.
- **The page** — `ProjectDetailController::show()` sends a v2 slug past `showUae()` into
  `malaysiaPageProps()`, and in the portal chrome adds `backUrl` = the UAE v2 tab
  (`portalBackUrl()`): the Malaysia-format page shows a *Back to project list* link there
  (`ProjectDetailContent.vue`), since the portal hides the public breadcrumb trail (2026-10-09).
- **The gate** — `CatalogueDetailService::memberMaySeeUaeV2()`: signed in and holding
  `Feature::NEW_PROJECTS` (admins only while `ANALYZE_PROPERTY_LOCKED` is on, matching the listing).
  `viewerMaySee()` and `previewableProject()` both honour it, so the page and every lazy JSON tab
  (analysis, supply, projection) open for the member and stay 404 for a guest.

### The engine, per market

`config/markets.php` has an **`AE`** profile: currency AED, neutral segment labels, AED-scaled buyer
thresholds, a monthly rent band of AED 1,000–250,000 — which the engine also sends as
`rental.rent_sanity`, so the layout-rent reader (`RentalPrediction::rentBand()` in PHP,
`petaRentBand` in JS) forms comparables on the same band; until 2026-10-11 both hardcoded
Malaysia's RM 200–50,000, every Dubai villa contract above AED 50,000 fell out, and a 2,812 sqft
Taormina Village villa was quoted the pooled median of three Al Barari mansions (AED 66,667) —
UAE developer / mall / school lists, and
**`market_provider` = `bayut`**. `MarketProfile::marketProvider()` (default `edgeprop`, so MY is
unchanged) is what `AnalysisEngineService` now reads its nearby evidence sources from.

The new-project age rule (`filterRecentDevelopments`, completion after 2016) applies unchanged:
Bayut buildings with a guide carry a completion year and pass it when recent, GPS-only buildings
carry none and drop out, so a launch is priced against recent stock's sales rather than decade-old
ready stock — the benchmark the plan's prototype showed is needed (plan §7). When no neighbour has a
year the engine falls back to the whole pool.

Bayut evidence rows use the engine's existing listing keys — `price_rm` / `psf_rm` hold **AED**.
They are schema names, not a currency claim; renaming them would touch every MY reader.

**The engine reads catalogue rows on the SUBJECT PROJECT's connection (2026-10-09).**
`RunPropertyAnalysis` passes `connection` = the connection the federation found the project on,
and `AnalysisEngineService` (plus `FindNearbyProjectSupply`) runs every `CatalogProject` /
`CatalogProjectSource` / floor-plan / analytics read there — a project that lives in a
deployment's OWN rows has its neighbours beside it, not on the master. Before this the engine was
pinned to the catalogue connection, so on wk (which reads the master live) a Bayut project's
Investment Analysis threw *No comparable projects found within 2 km* although 256 Bayut rows sat
within 2 km in wk's own database. Master projects are unaffected: their connection IS the
catalogue. `market_airbnbs` stays on the catalogue connection (market data, not catalogue rows).

### The Buying Guide tab (2026-10-10) — when the cash is needed

Owner: *"oversea buyer wanna know the payment timeline, when need the cash"*, a separate tab like Hong
Kong's. On a UAE v2 page the Malaysia-format page gains a **Buying Guide** tab (`UaeBuyingGuideTab.vue`,
between Amenities and Developer Record; members only, like Units · Price). Five blocks, numbered as the
Hong Kong guide's: ① cash to prepare (the developer's instalments on the selected layout as three sums —
before, at and after handover — with a handover-mortgage switch, plus the one-off purchase costs);
② the payment timetable, every instalment dated from today and the developer's handover date; ③ funds
needed by date, the running total; ④ holding costs per year (service charge typed by the member, the
figure is the building's); ⑤ selling later.

- **Inputs** — `ProjectDetailController::show()` adds `buyingGuide` for a UAE page:
  `BuildUaeBuyingGuide::execute()` reads the Property Finder source's `payment_plans` (normalised to
  `[{title, phases: [{key, pct, milestones: [{label, pct}]}]}]`, unknown phases and bare strings dropped),
  the handover date (`completion_date`, else the construction timeline's *Expected Completion*), and the
  cost table **`config/uae_buying.php`**. 2,666 of the 2,990 projects carry a plan; a project without
  one says so and still lists the one-off costs.
- **Dates** — `utils/uaeBuyingGuide.js`: `parseMilestone()` reads the wordings the file uses ("On
  Booking", "Within N months from booking date", "(1 % monthly)", "N days after the reservation", "On
  Handover", "N months after handover", a month and year); an instalment with no wording takes its
  phase's default, and an undated construction share is shown as the period it falls in, marked
  estimated. `scheduleRows()`, `fundsByDate()`, `cashSplit()`, `handoverMortgage()`, `exitCosts()` are
  pure and tested (`uaeBuyingGuide.test.js`).
- **The cost table is an ASSUMPTION set** — DLD 4 %, Oqood, admin, agency, the mortgage cap and rate,
  the service-charge default, agency and NOC on exit, the resale threshold — printed beside each figure
  on the tab as "PropertyLab's standard assumptions" until the owner confirms them (`confirmed` in the
  config). Change a figure there, never in the component.
- Tests: `tests/Unit/Actions/BuildUaeBuyingGuideTest.php`, the `buyingGuide` assertion in
  `UaeV2ProjectAccessTest`, `resources/js/utils/uaeBuyingGuide.test.js`,
  `UaeBuyingGuideTab.test.js`.

### The Amenities tab, UAE version (2026-10-10)

Owner: *"the amenities might need to redesign for UAE market. no point mention t20 etc as this is more
for malaysia."* On a UAE v2 page the Amenities tab renders **`UaeAmenitiesPanel.vue`** instead of the
Malaysian `AmenitiesPanel` (no T20 / M40 / B40, no BMS signals, no Tier-1 mall stars, no Malaysian
school lists). Three blocks:

- **What's nearby, with real travel times** — Metro & tram (on foot), malls, international schools,
  hospitals & clinics, supermarkets, beaches & parks, airports (by car): **`ResolveUaeGoogleAmenities`**,
  one Google Places Nearby Search per type (closest first, a keyword where the type is too broad) and one
  Distance Matrix call per category, ranked by minutes, cached 30 days by coordinate — the Hong Kong
  location panel's method, without its curated rail table. Categories in **`config/uae_amenities.php`**;
  the key is `services.google_maps.key`. Drawn on a Leaflet map with the project at the centre.
- **Who buys here** — the UAE reading from **`amenity_demand_ae.md`** (`AiRequest::PROMPT_AMENITY_DEMAND_AE`):
  the community's character, 4–6 buyer personas in AED with **Upper / Middle / Lower** spending power
  (the `AE` market profile's segments, never nationality), premium signals, concerns, outlook. The
  model is told the nearby places WITH their travel times.
- **Holiday-home potential** — short-let demand as an **AI estimate**, labelled so: nightly rate in AED
  for a 1-bedroom, occupancy, monthly revenue, peak season (Nov–Apr), guests, competition and the
  emirate's licensing (Dubai's DET holiday-home permit).

**How it is served.** The page's one `amenity-demand` call: `ProjectDetailController::amenityDemand()`
branches on the UAE to `uaeAmenityDemand()`, which returns `nearby` (the categories) beside the usual
`ai_status` / `ai_analysis`. The reading is STORED once per project (`LocationInsightStore`, on the
project's own connection — wk's own rows included) and generated only when there is none; a UAE page
fetches as soon as the tab opens, since nothing there waits on a layout's analysis. Tests:
`tests/Feature/Actions/ResolveUaeGoogleAmenitiesTest.php`, the amenity assertion in
`UaeV2ProjectAccessTest`, `UaeAmenitiesPanel.test.js`.

⚠️ **"On the project's own connection" was not true until 2026-10-10 evening.** `CatalogAiContent` is
pinned to the catalogue connection, and `CatalogAiContentRepository` queried it bare, so for a wk-own
project the version lock and the insert went to the MASTER — `1142 … command denied … catalog_ai_contents`
on every page view, the reading was never stored, and `source` stayed `generated` (the 7-day Redis
entry answered, and would have paid for a new AI call the day it lapsed). The repository now reads and
writes on `$catalogue->getConnectionName()` (`connectionOf()`); test
`CatalogAiContentTest::test_content_lives_on_the_projects_own_connection`.

**Two things that made every page view slow on wk (2026-10-10), and what changed:**

- **wk's Google Maps key is EXPIRED** (`GOOGLE_MAPS_API_KEY`; Places answers `REQUEST_DENIED — The
  provided API key is expired`). `ResolveUaeGoogleAmenities` refuses to cache an empty answer for the
  month (right: a renewed key must take effect), so every page view re-fired nine denied Places calls —
  ~0.6 s each time, for nothing. A refusal is now remembered for **15 minutes** per spot
  (`REFUSAL_MINUTES`, key `uae-amenities:<v>:<lat>_<lng>:refused`) and written to the log once per
  window with Google's reason. Renewing the key is still the fix for the tab: until then the UAE
  Amenities tab shows no nearby places at all.
- **The Investment tab no longer waits on the amenity call.** `investmentAnalysisLoading` in
  `ProjectDetailContent.vue` gated the whole tab on `amenityAiLoading` as well as the analysis, so a
  page whose numbers arrived inline (`analysisSeed`) still opened on *Crunching the numbers…* for the
  length of that second request. It now waits on the analysis alone; the reading's one card on the
  Summary sub-tab (`demand` → `ProjectInvestmentSummary`) renders when it lands.

### New Supply on a v2 page (2026-10-10)

`FindNearbyProjectSupply` mirrors the Malaysian rule — other PUBLISHED new-project rows within 3 km —
and the whole v2 family is unpublished by design, so every v2 page said *No other new launches found
within 3 km* (Nautis Residences: 151 Property Finder launches within 3 km, none shown). For a subject
`rendersAsUaeV2()`, the finder now swaps `published()` for `BuildNewProjectListing::uaeV2Scope()` — the
same rule that makes a row a v2 project — on the subject's connection; the Investment tab's
`result.new_supply` is the same list. A neighbour the OLDER feed also carries, or one with no source,
is not listed. Test: `ProjectDetailSupplyTest::test_a_uae_v2_subject_lists_the_unpublished_property_finder_launches_around_it`.

### The front end

`projectInvestment.js` exports `investmentMarket` (`{ symbol, iso2 }`), set once by
`ProjectDetailContent` from `detail.pricing.currency` and the country slug. `formatMoney()` and the
Summary, Market Value, Whole-Unit Rental and Selected-Unit components print its symbol; the
Malaysia-only figures above check `investmentMarket.iso2 === 'MY'`. Airbnb tabs are unchanged —
there is no UAE Airbnb feed, so they show their own empty state.

### Getting data onto it

Two feeds, two roles:

```bash
# EVIDENCE — Bayut's ready buildings with DLD sales + Ejari rents (subsale only; project:* skipped)
php artisan catalogue:scrape-bayut
php artisan catalogue:sync bayut                                   # on the Hub; on wk see below

# SUBJECTS — Property Finder's new projects, matched to Bayut's building GPS
php -d memory_limit=2G artisan catalogue:scrape-pf-new-projects    # → pf_new_projects_<stamp>.jsonl.gz
php artisan catalogue:match-pf-bayut … && php artisan catalogue:judge-pf-bayut …   # → the matched file
php artisan catalogue:sync propertyfinder-nl --file=/path/pf_new_projects_<stamp>.jsonl.gz
```

`PropertyFinderNewProjectsAdapter` streams the matched JSON Lines file line by line (never whole:
134 MB decoded) into the standard contract via `PropertyFinderProjectNormalizer::catalogueRecord()`
— [propertyfinder-new-projects.md](/docs/modules_handbook/shared/project-catalogue/propertyfinder-new-projects.md)
has the field map. Photos, brochures and drawings stay on Property Finder's CDN (`CatalogMedia::resolveUrl()`
falls back to the URL; the CDN serves them with our referer). Rents and sales are DLD —
**Dubai only**; projects elsewhere get layouts but no market value or rental.

**Onto the master:** neither file has reached `master_projects` yet (2026-10-13) — the Hub import,
file by file with the expected run stats and the provider-id check, is
[uae-v2-hub-import.md](/docs/modules_handbook/shared/project-catalogue/uae-v2-hub-import.md).

### On wk (loaded 2026-10-09) — the rows live in wk's OWN database, beside the master

> **Bayut is subsale only (owner, 2026-10-09 evening).** The 2,998 Bayut new projects described below
> were retired the same evening (`catalogue:retire-bayut-new-projects --apply`, Run #14: 2,998 sources
> and 19,175 media deactivated, 2,687 projects removed, 311 towers kept as subsale buildings). What
> remains of Bayut on wk is the subsale set: 12,247 ready buildings with their DLD sales, Ejari rents and
> derived layouts. Runbook rule 7.
>
> **Property Finder's new projects loaded the same night (`propertyfinder-nl`, Run #15):** the
> matched hand-off `pf_new_projects_20261009_final.jsonl.gz` (2,990 projects) through
> `storage/app/catalogue/pf-nl-sync-20261009.php` — the same redirect wrapper, provider
> `propertyfinder-nl`. 2,990 created, 0 updated, 0 failed in 32 min → 15,085 own AE rows, 2,984 of the 2,990
> with coordinates, 152 attached to a kept Bayut tower. Verified through the HTTP kernel as an admin: Golf
> Grand (Dubai, Bayut pin) → FAIR PRICE, AED 2,246 vs market 2,458 psf, rent AED 8,948, yield 7.0 %; The
> Meriva Collection (Dubai, Property Finder pin) → OVERPRICED; Al Ghadeer Gardens (Abu Dhabi) renders its
> layouts but the analysis answers *No comparable projects within 2 km* — the DLD ledger is Dubai's, as before.
>
> **Reloaded from the FINAL data set (version 3) the same night under the owner's display rules**
> (runbook rule 8): only showable unit types are layouts, every photo is copied to our disk before it
> shows. Run #17 [success] propertyfinder-nl/AE: 0 created, 2,990 updated, 0 failed (34 min, 23:48–00:22 MYT; Run #16, the same file under the stricter first wording of rule 1, was stopped mid-run and marked aborted) → 9,351 layouts on 2,689 projects, every one priced AND sized, 7,729 of them with a drawing; 57,029 media rows held inactive until `catalogue:store-pf-media` copies them (started 00:25 MYT, heroes first); the UAE v2 tab reads 2,990; 08 Life Residences (sizes filled from recent sales) now analyses as FAIR PRICE.

wk reads the shared master live (`CATALOGUE_USE_DEFAULT_CONNECTION=0`, SELECT-only account), so
`catalogue:sync bayut` cannot write where the models point. It did not need to: the New Projects
listing and the project page both go through `CatalogueFederationService`, which unions the master
with this deployment's own rows (`origin = own`, ids in the offset space ≥ 1,000,000,000). The two
crawl artifacts were therefore ingested into `petav3wk` with the `catalogue` connection redirected
**inside that one process only** — the cached site config is untouched and the site never flipped:

```php
// php artisan tinker --execute="require 'this-file.php';"
config(['database.connections.catalogue' => config('database.connections.' . config('database.default'))]);
DB::purge('catalogue');
if (DB::connection('catalogue')->getDatabaseName() !== 'petav3wk') { throw new RuntimeException('refusing'); }
Artisan::call('catalogue:sync', ['provider' => 'bayut', '--file' => $path, '--no-interaction' => true]);
```

`catalogue:store-bayut-media` runs the same way (it writes on the owning row's connection). Run it for **all four kinds** — `hero`, `gallery`, `document` AND `floor_plan` — the first wk pass (2026-10-09) listed three and left the 909 Business Bay drawings on Bayut URLs until a separate `--kind=floor_plan` pass. Result:
3,196 own AE rows (2,998 projects + Business Bay's buildings), 1,671 floor plans; the tab shows 2,537.
Both artifacts sit in `storage/app/catalogue/inbox/bayut/processed/`; the sync does not move files,
and it takes the oldest `*.json` in the inbox ROOT, so leave that root empty.

**Subsale buildings (2026-10-09 12:08 MYT):** a third artifact, `bayut_subsale_merged_20261009.json` —
12,247 ready buildings UAE-wide (`market_segments: ["subsale"]`), 6,003 of them with 12 months of DLD
sales + Ejari rents, 2,975 with a building guide — the cloud crawl's `building:*` records merged with
its building-guide file BEFORE loading. The tab count is unchanged (it counts the new-project segment);
these rows are the neighbours the engine reads for Market Value and Rental. Run #13: 12,034 created,
213 updated, 0 failed → 14,934 own AE rows; 296 buildings attached by name to the Bayut project that is
the same tower; the merge's resolve step (`ProjectRepository::syncCatalogFloorPlans`) minted 37,077 subsale layouts (rent median + market value, no
price) for 5,853 buildings from their sales/rent rows. The new-project half of that crawl is held back
for the Property Finder merge.

Two things that bite:

- **Do not switch wk to COPY mode for this.** Its copy (last mirrored 2026-09-14) lacks the 951
  PropertyFinder UAE rows and every publication date, so every other country tab reads 0 the moment
  the flag flips (seen 2026-10-09, reverted within minutes).
- **`catalogue:mirror-from-master --apply` deletes every local-only row except `media`** — that is
  the whole Bayut set. Until the master carries Bayut, never run it on wk. And once the master DOES
  carry a market (the Hub imported UAE v2 + Bayut on 2026-10-13/14), the federation lists each of its
  projects twice until wk retires its own copy — with `catalogue:retire-own-rows --country=AE`, one
  market at a time (the mirror would also erase the next market still waiting for the Hub, Singapore
  on 2026-10-14). See [uae-v2-hub-import.md](uae-v2-hub-import.md) *Then tell wk*. Bayut reaches the master
  only through the Hub (`catalogue:sync bayut --full` there); master `data_providers` still ends at
  id 9, so the Propin and NuProp artifacts of 2026-09-27 are in the same queue.
- **Several artifacts naming the same `building:*` / `project:*` keys: merge them into one first.**
  `ProjectCatalogueMergeService::upsertSource` REPLACES a source's `fields` on update, so the last file
  wins wholesale — a guides file with no evidence would blank the sales and rents the evidence file
  loaded. Runbook rule 6 has the merge that was used.
- The tab counts are cached for 10 minutes (`BuildNewProjectListing::AGGREGATE_TTL`, keys
  `np-listing:*` in Redis); flush them after a load or the tab lags the data.

## Related files

- `app/Services/Property/CatalogueDetailService.php` (`UAE_V2_PROVIDER`, `rendersAsUaeV2`, `memberMaySeeUaeV2`, `viewerMaySee`)
- `app/Actions/BuildUaeBuyingGuide.php`, `config/uae_buying.php`, `resources/js/utils/uaeBuyingGuide.js`, `resources/js/Components/ProjectDetail/UaeBuyingGuideTab.vue` — the Buying Guide tab
- `app/Actions/ResolveUaeGoogleAmenities.php`, `config/uae_amenities.php`, `resources/prompts/amenity_demand_ae.md`, `resources/js/Components/ProjectDetail/UaeAmenitiesPanel.vue` — the UAE Amenities tab
- `app/Services/Property/Ingestion/Adapters/PropertyFinderNewProjectsAdapter.php` + `app/Services/Property/Scraping/PropertyFinderProjectNormalizer.php` (`catalogueRecord`) — the subjects' importer
- `app/Actions/BuildNewProjectListing.php` (`UAE_V2_TAB`, `uaeV2Scope`, the tab), `app/Http/Controllers/Main/Portal/AnalyzePropertyController.php`
- `app/Actions/FindNearbyProjectSupply.php` — New Supply; a v2 subject's neighbours are the v2 set, not the published set
- `src/Analysis/Repositories/CatalogAiContentRepository.php` (`connectionOf`) — AI content, the stored amenity reading included, follows the project's connection
- `app/Http/Controllers/Main/Site/ProjectDetailController.php` (`show`, `isUaeV2`, `previewableProject`)
- `config/markets.php` (`AE`), `src/Common/Support/MarketProfile.php` (`marketProvider`), `src/Analysis/Services/AnalysisEngineService.php`
- `config/project_catalogue.php` (`uae_v2.enabled`)
- `resources/js/Components/ProjectDetail/projectInvestment.js` (`investmentMarket`) and the components named above
- Tests: `tests/Feature/Property/UaeV2ProjectAccessTest.php`, `tests/Feature/Console/SyncPropertyFinderNewProjectsTest.php`,
  `tests/Unit/Scraping/PropertyFinderProjectNormalizerTest.php`, `tests/Unit/Common/MarketProfileTest.php`,
  `tests/Unit/Scraping/BayutNormalizerTest.php`, `tests/Feature/Main/Portal/Analyze/NewProjectsTabTest.php`
