# Singapore — the fourth market, from the owner's URA / HDB hand-off

> 📍 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 pattern
> it follows is Hong Kong's ([hk-layout-analysis.md](/docs/modules_handbook/shared/project-catalogue/hk-layout-analysis.md))
> for the evidence and the UAE's ([uae-v2.md](/docs/modules_handbook/shared/project-catalogue/uae-v2.md))
> for the launches. The portal tabs it feeds are documented in
> [main/analyze-property/readMe.md](/docs/modules_handbook/main/analyze-property/readMe.md) and
> [main/property-research/readMe.md](/docs/modules_handbook/main/property-research/readMe.md).

Built 2026-10-14. The owner's ask: *"does all the data sufficient for me to launch the singapore
portal and the new project analysis can fit to my format like the malaysia and UAE portal? then
layout roi summary also can be populate. other tab like subsale analysis, property explorer, heat
map, ai advisor all can support"* — then *"start now"*. Four of the five tabs, on the same engine
and the same format; the AI Advisor stays Malaysian (it reads the realtycheck archive only, as it
does for HK and the UAE).

## What it does

Singapore (`countries.iso2 = SG`, S$, SGD) is a market of the catalogue, with:

| Tab | What a member sees | Where it comes from |
|---|---|---|
| Analyze Property → **New Project Analysis → Projects** (`?country=sg`) | The Singapore launches as cards, each opening the **Malaysia-format** project page — layouts with a price, market value, nearby rental, the summary — members-only and unpublished, exactly like the UAE v2 set | provider **`edgeprop-sg`** (the hand-off's launch list + 99.co detail + per-unit stock), `SingaporeNewProjectsAdapter` |
| New Project Analysis → **Layout ROI Summary** (`?country=sg`) | One row per Singapore layout in S$, SGD price bands, the one loan yardstick | `layouts:project --country=SG` over the launches' layouts and the URA ring |
| **Subsale Analysis** (`?market=sg`) | Market Value Checker and Rentalizer for a pin in Singapore, with the MAS loan prefill (75 % / 3.0 % / 30 years, editable) | the same ring; `config/markets.php` `SG` |
| **Property Explorer** / **Heat map** (`?country=sg`) | Every Singapore estate with caveats since Oct 2021, its median price and strata PSF, the monthly series; S$ heat bands | provider **`ura`** (the ledger as one evidence source per estate, which also MINTS the estate rows), `SgRecordedSales` |
| AI Advisor | Not on Singapore (nor HK, nor the UAE) | — |

## The hand-off

`singapore_database.tar.gz` (24 MB, from the owner's dev box `peta_wk_dev`, 2026-10-14): a MySQL
dump of six `ih_sg_*` tables plus one CSV per table — URA REALIS and HDB public data, no personal
data. What is in it and what the catalogue uses:

| Table | Rows | Period | Used as |
|---|---|---|---|
| `ih_sg_private_txn` — private residential caveats | 132,199 | Oct 2021 → Oct 2026 | the **ledger's sales** (`market:import-sg`); 58 bulk deals (noOfUnits > 1) left out |
| `ih_sg_private_rent` — rental contracts | 246,657 | Jan 2024 → Aug 2026 | the **ledger's rents**; URA publishes a size BAND per contract, the midpoint is the row's area |
| `ih_sg_newproj` — EdgeProp SG's launch list, 99.co's detail JSON | 103 | current | the **launches** (`sg_new_projects_<stamp>.jsonl.gz`) |
| `ih_sg_units` — the developer's per-unit stock | 25,982 on 64 launches | to Jul 2026 | the launches' **layouts** (banded) |
| `ih_sg_hdb_txn` — HDB resales | 242,454 | Jan 2017 → Oct 2026 | **not loaded** (HDB is out of scope at launch; the dump is kept) |
| `ih_sg_hdb_rent` — HDB median rents | 13,305 | 2005 Q2 → 2026 Q2 | not loaded |

Facts that shaped the design, each checked on the file:

- Every caveat names its project in one UPPER-CASE name and 78 % carry GPS (2,826 of 2,973
  projects have at least one located caveat); 1,493 condos have three or more sales in the last 24
  months. The `tenure` is free text in 142 spellings ("99 yrs lease commencing from 2018").
- Rents have no GPS and no exact size; 94 % join to a sales project by name, which is where the
  estate's pin comes from.
- 87 of the 103 launches appear in the caveats by name; 74 carry unit types (size, bedrooms, a
  drawing, **no price**), 64 the per-unit stock (sold prices), 7 nothing but a name and a photo.
  `totalUnits` is blank on every launch; 22 have no photo; 18 no handover year; the handover field
  comes in four formats.
- Photos and drawings are hot-linked to `pic2.99.co` and `sg.tepcdn.com`; the launch list links
  `www.edgeprop.sg`. Every image is copied to our storage before it is shown (the UAE rule 3).
- Every id in the dump is even and the counters are twice the row counts: the source table was
  loaded twice and deduplicated before export. Harmless.

The hand-off is imported into the local scratch database `sg_property_scratch` on wk for
querying; the launch artifact is built from it with one `mysql … JSON_OBJECT(…)` export per project
(the recipe is at the end of this file). The CSVs' `raw` / `detail` JSON columns are NOT valid CSV
(their inner quotes are not doubled) — read those two columns from the dump, never the CSV.

## How it works

### 1. The ledger — `market:import-sg`

[`ImportSingaporeMarketLedger`](/app/Console/Commands/ImportSingaporeMarketLedger.php) streams the
two CSVs into `market_transactions` (country SG) on the **catalogue connection**, the table Hong
Kong's Land Registry copy lives in, so every reader of that shape works unchanged:

| Column | Sales (`post_type S`) | Rents (`post_type R`) |
|---|---|---|
| `external_id` | `sg-sale-{id}` | `sg-rent-{id}` (a reload is an upsert) |
| `estate_name` / `canonical_estate` | the project, as URA prints it | the project |
| `price` | the caveat price | the **monthly** rent |
| `net_area` / `net_psf` | strata sq ft / S$ psf | the band's midpoint / rent ÷ area |
| `registered_at` = `instrument_at` | the contract MONTH (the file has month precision) | the lease month |
| `sale_type` | `NewSale` / `SubSale` / `Resale` (URA 1 / 2 / 3) | — |
| `district` = `area_code` | `01`…`28` | same |
| `floor` | URA's floor range (`26-30`) | — |
| `raw` | property type, market segment, tenure text, foreigner-buyable, the caveat's GPS | property type, the size band |

[`SgMarketLedger`](/app/Support/SgMarketLedger.php) is what every reader asks: **where** the ledger
is (the catalogue connection, else the site's own copy — `readConnection()`, the UaeRecordedSales
master-first-else-local rule, because on wk the Hub has not loaded it) and **when** it is from
(`asOf()`, the newest sale's contract month — every window is measured from it, never from today).

### 2. The estates and the ring — `catalogue:sync ura`

[`UraLedgerAdapter`](/app/Services/Property/Ingestion/Adapters/UraLedgerAdapter.php) is
`HkLandRegistryAdapter` with one difference that is a fact about Singapore: **there is no estate
feed, so the estates are minted from the ledger.** One record per project name with evidence
(≥ 3 sales or ≥ 3 rents in the 24 months before the as-of month, and at least one located caveat):

- attached to the one Singapore row of that NAME when it exists (a launch the EdgeProp feed carries,
  or an estate from an earlier run — the subsale row wins a duplicate, HK's rule), else a NEW row
  (`attach_only` false, `canonical_facts` true — the source carries the facts that make the row:
  the name title-cased, the median GPS of its caveats, `Condominium/Apartment`, the tenure, the
  district (`area`), the region (`state`: Core / Rest of / Outside Central Region), the address);
- with the HK evidence shape on the source: `asking_sale_listings` / `asking_rental_listings`
  (newest 150 each, `price_rm` / `psf_rm` / `sqft` / `bedrooms` — rents carry bedrooms; a caveat
  does not, so a sale's `bedrooms` is **estimated from its strata area** in the launches' own size
  bands (`UraLedgerAdapter::bedroomsFromArea`, flagged `bedrooms_estimated`) because the engine
  filters comparable sales by bedroom count), `psf_median` / `psf_25` / `psf_75` / `price_median`, `total_transactions`,
  `quarterly_sale_psf` (12 quarters — the engine's growth reading needs 6), `market_segments`
  `[subsale]`;
- **private non-landed only**: Apartment, Condominium, Executive Condominium. URA files every
  landed caveat of a street under "LANDED HOUSING DEVELOPMENT", which is not an estate, and the
  engine's type gate refuses detached houses anyway — a landed launch finds no ring (6 of the 103),
  as a Dubai villa enclave finds none.

`config/markets.php` `SG` names the provider (`market_provider` = `ura`), S$, the MAS loan prefill,
a rent band of S$ 800–40,000 a month, the PSF thresholds, developer / mall / school lists.
`MarketProfile('SG')->marketProvider()` is what the engine reads its nearby sources from; nothing in
the engine is Singapore specific.

### 3. The launches — `catalogue:sync edgeprop-sg --file=…`

[`SingaporeNewProjectsAdapter`](/app/Services/Property/Ingestion/Adapters/SingaporeNewProjectsAdapter.php)
streams `sg_new_projects_<stamp>.jsonl.gz` (one launch per line; inbox
`storage/app/catalogue/inbox/edgeprop-sg/`) through
[`SingaporeProjectNormalizer`](/app/Services/Property/Scraping/SingaporeProjectNormalizer.php) and
the shared artifact contract. The field map:

| Catalogue | From the line |
|---|---|
| `project_name`, `developer` | `name`, `developer` |
| `latitude` / `longitude` | EdgeProp's pin (93 % have one) |
| `area` / `state` / `address` | the district's name / its region / "District 26, …" (`SgDistricts`) |
| `property_type` | Condominium, Apartment, Executive Condominium, Mixed-Use → Condominium/Apartment; Landed → Terrace House |
| `tenure` | `99 years` / `999 years` → Leasehold, Freehold, `-` → none; the years ride as `tenure_years` |
| `completion_year` / `completion_date` | the TOP date, else `completion` in any of its four formats (`2029`, `Q3 2029`, `May 2023`, `9 January 2031`) |
| `sale_status` | Completed when the handover year has passed, else New Launch |
| `price_min` / `price_max` | derived from the priced layouts (`plan_derived_price_providers`); 99.co's range is the fallback |
| `market_segments` | `[new_project]` |
| Floor plans | **the layouts below** — a price AND a size (the UAE rule as settled 2026-10-09) |
| Media — every entry **held** | the EdgeProp thumbnail as hero, the 99.co photos as gallery, one drawing per layout; shown only once `catalogue:store-sg-media` has copied the file |
| Source-only (`SingaporeProjectNormalizer::SOURCE_FIELDS`) | the EdgeProp asset id and URL, sold %, average PSF, tenure years, district code, segment, TOP date, 360 flag, the unit-type count, **`unit_bedrooms`** (the card's bedroom mix — the shown layouts only), units total / sold, the per-bedroom PSF, 99.co's price range, how many layouts were priced from what |

**The layouts** ([`SgUnitLayouts`](/app/Services/Property/Ingestion/Adapters/SgUnitLayouts.php)):
the launch's units — the developer's stock where the hand-off has it, else the portal's unit types
(a median of 14 distinct sizes per project, far too fine) — banded exactly as Hong Kong's are: one
layout per bedroom count at one size band (`SIZE_STEP` 12 %, `SIZE_SPAN` 25 %), the band's median
size, `units_count`, the band's commonest drawing (or the nearest unit type's of the same bedroom
count). Then **each band is priced from what its buyers actually paid**: the median of the
project's URA new-sale caveats whose strata area falls in the band (± 3 %), the 24 months to the
as-of month, when three or more exist (`SgMarketLedger::newSalePrice`); else the band's own sold
prices; else the portal's per-bedroom PSF (or EdgeProp's project PSF) on the band's size. A band
with no price at all is not a layout. `source_fields.price_basis` says which (`caveats` /
`sold_units` / `portal_psf`), with the caveat count. `source_key` is the band's bounds
(`layout:2:732-743`), never an ordinal — the HK collision lesson.

**Attachment** is the crawls' rule (an existing provider link; else exact name + 5-decimal
coordinates) and then one more: the one Singapore row of the launch's NAME, case and whitespace
folded (`resolveCanonicalId`) — the estate the ledger minted under the same name, pinned at its
caveats' GPS rather than EdgeProp's. The row then carries the developer's layouts and the ledger's
evidence, which is the identity the page prices against; two rows of that name refuse to guess.

### 4. The portal route — "portal launches", one table per country

Before 2026-10-14 the Malaysia-page route for a foreign feed was hard-wired to the UAE in ten
places (`rendersAsUaeV2`, the listing's `$uaeV2`, the `ae-v2` tab, the controller's mapping, the
supply action, the layouts command…). It is now ONE table,
**`CatalogueDetailService::PORTAL_LAUNCH_PROVIDERS`** (`AE` → `propertyfinder-nl`, `SG` →
`edgeprop-sg`), read by:

- `CatalogueDetailService::portalLaunchProvider($iso2)` / `rendersAsPortalLaunch()` /
  `memberMaySeePortalLaunch()` — `rendersAsUaeV2()` and `memberMaySeeUaeV2()` are now the UAE's
  wrappers over them (the UAE keeps its one exclusion: a row the OLDER PropertyFinder feed carries
  stays on its old page);
- `BuildNewProjectListing` — `$portalLaunch`, `portalLaunchScope($query, $provider)` (`uaeV2Scope`
  delegates), the cards' `unit_bedrooms` from the market's provider, and **a portal-launch market's
  own country tab counts and opens its portal list** (Singapore has no published launch and no
  legacy feed, so it needs no `sg-v2` tab — the UAE keeps its v2 tab as before);
- `AnalyzePropertyController::newProjects` (`?country=sg` → provider `edgeprop-sg`),
  `ProjectDetailController::previewableProject`, `FindNearbyProjectSupply`, `layouts:project`.

The price-band filter on the listing now uses the market's own bands (`PRICE_BANDS_SGD`: under
S$ 1.5M / 1.5–2.5M / over 2.5M, mirrored in `newProjects.js`) — it used to apply the ringgit
bands to every market.

### 5. The research tabs

`ResearchMarket::PROFILES` `SG` (home Marina Bay, region word "Region", area basis built-up — URA
records strata area). [`SgRecordedSales`](/src/PropertyLab/Research/SgRecordedSales.php) is
`HkRecordedSales` on the Singapore ledger (one daily aggregate of every caveat since Jan 2021,
keyed by project name, on `SgMarketLedger::readConnection()`); `CatalogueExplorerIndex::singapore()`
lists every located Singapore row whose name has caveats, **on both catalogue sides** (on wk the
rows are the site's own); `CatalogueExplorerEvidence` prints the strata-PSF basis and the Singapore
caveats' warnings. Heat bands in `heatmapModel.js` (`SG`: S$ 1,200–3,500 psf, S$ 1–5M), the
Explorer's price-cap steps (`ExplorerPanel.vue` `SGD`).

Members see **published-and-listed rows only** (the 2026-09-27 ruling), so the estates are
published by `catalogue:sg-publish-estates` — the rows with a `ura` source and NO launch feed; a
launch is a portal row and never published. That is why `ura` is not `publish_on_ingest` (that
flag publishes every row a run touches, launches included). The Singapore completeness waivers
(`detail_contract.waived_by_country.SG`: developer, hero media, floor plans, completion) say what
a public-record estate genuinely lacks.

### 6. Subsale Analysis

`SubsaleAnalysisController::markets()` lists every market with a profile, so Singapore appears by
itself: S$, the ring above, the MAS prefill, `rent_sanity`, the Marina Bay centre from the
research profile. `RunSubsaleAnalysis::EVIDENCE['SG']` is the page's evidence line.

## The Hub runbook

Every step writes the master (`CatalogueFederationService::consoleMayWriteMaster()`), in this
order — the launches' band prices read the ledger, the estates attach to the launches by name:

```bash
php artisan migrate --path=database/migrations/catalogue --database=catalogue   # SG country row + the two providers, master ids
php artisan migrate                                                              # …the site copies (same ids), the market-site attachment
php artisan market:import-sg --dir=/path/to/handoff/csv                          # the ledger (sales + rents), ~8 min
php artisan catalogue:sync edgeprop-sg --file=/path/sg_new_projects_<stamp>.jsonl.gz --full   # the launches
php artisan catalogue:sync ura --full                                            # the estates + the ring
php artisan catalogue:sg-publish-estates                                         # estates only
php artisan catalogue:store-sg-media --kind=hero; --kind=floor_plan; --kind=gallery
php artisan layouts:project --country=SG --run                                   # the Layout ROI Summary rows (--fresh to re-price)
```

A ledger refresh is `market:import-sg` again (an upsert), then `catalogue:sync ura --full` (the
ring) and `layouts:project --country=SG --run --fresh`; a launch refresh is a new artifact and
`catalogue:sync edgeprop-sg --file=… --full` (a launch the new file no longer lists is retired).

## Proving it on wk (read-only master) — `scripts/sg-market-on-site.php`

wk reads the master live and cannot write it, so the whole market was loaded into wk's **own rows**
(`origin = own`) through the process-local redirect of the uae-v2.md "On wk" recipe, inside one
tinker process, with the edit domain widened for `layouts:project`
([`scripts/sg-market-on-site.php`](/scripts/sg-market-on-site.php), `SG_STEP=ledger|launches|evidence|publish|media|project|all`):

```bash
SG_CSV_DIR=…/sgdb/csv SG_FILE=storage/app/catalogue/inbox/edgeprop-sg/sg_new_projects_20261014.jsonl.gz \
  php -d memory_limit=2G artisan tinker --execute="require 'scripts/sg-market-on-site.php';"
```

The master wins the moment the Hub loads Singapore: `SgMarketLedger::readConnection()` and
`BuildLayoutTable::sourceFor()` both read the master first. Until then wk's rows are what a member
sees, computed by the same code on the same data the Hub will use.

**Loaded on wk 2026-10-14** — see the run log `storage/logs/sg/` and the numbers at the end of
this file's *State* section.

## Decisions (mine, defaults the owner did not object to — his calls to reverse)

- **Financing prefill** 75 % / 3.0 % / 30 years (MAS first-loan cap, an indicative 2026 rate);
  the member edits. **Layout ROI loan** stays the one yardstick (100 % / 4 % / 35 years) by the
  owner's 2026-10-12 ruling.
- **Rent sizes are bands**, so a Singapore rent PSF reads a few percent coarser than HK or Dubai;
  the yield column is unaffected in kind.
- **The 22 launches without a photo** stay hidden by the display rule (photo required for the
  card); the 7 with no unit data list with no layouts.
- **HDB** is out of scope at launch; the two HDB tables are in the dump for later.
- **Estates are published**, launches never. Reversible with `catalogue:unpublish`.
- **No Buying Guide tab yet** for Singapore: the UAE's reads a developer instalment plan the
  hand-off does not carry; Singapore's would show the standard progressive payment scheme and BSD /
  ABSD by buyer profile (60 % for a foreigner), which needs the owner's table.
- **The market chooser shows Singapore** (same day — the fourth panel, the Higgsfield picture, the
  phone grid: [main/cinematic-site/readMe.md](/docs/modules_handbook/main/cinematic-site/readMe.md)),
  but there is **no cinematic `/sg` page yet**: `/sg` opens the older Inertia home until the founder's
  package delivers one.

## State — wk's own rows, 2026-10-14 (logs in `storage/logs/sg/`)

| What | Count |
|---|---|
| Ledger: URA sales / rental contracts (`market_transactions`, country SG) | 132,141 / 246,657 — sales as of 2026-10-01 |
| Launches (`edgeprop-sg` sources, portal rows, unpublished) | 103, 81 with layouts |
| Layouts on the launches (a price AND a size) | 505 — 358 priced from the project's own caveats, 95 from its sold units, 52 from the portal PSF |
| Media copied to our storage | 1,165 (103 heroes, 452 drawings, 610 photos); 0 held |
| Estates minted from the ledger (`ura` sources) | 2,100 sources: 2,020 new estate rows + 80 launches that also carry the ring |
| Estates published (Explorer / Heat map) | 1,943 — 77 unpublished because they have rents but no sale in the window (no market price) |
| Property Explorer, Singapore | 2,105 rows (admin; the first daily aggregate takes ~34 s) |
| Layout ROI Summary (`layout_analyses`, SG) | 497 rows on 80 launches, 491 with a rent; verdicts UNDERVALUED / FAIR / OVERPRICED = 15 / 424 / 58 |
| Subsale Analysis | Market Value Checker and Rentalizer answer for a Singapore pin (Geylang 2-bed: market S$ 1,486 psf, rent S$ 4,500 from 129 contracts within 1 km) |

A launch's Investment Analysis reads OVERPRICED against the resale ring more often than not
(One Marina Gardens 1-bed: S$ 2,903 psf against a S$ 1,989 psf ring) — a new launch carries a
premium over the resale estates around it, which is the market, not a bug, exactly as in Malaysia.
Twenty-three launches have no layouts (7 with no unit data at all, the rest with units but no price
that passes the rule) and list as cards without the Units tab.

## Building the launch artifact from the hand-off (wk)

```bash
sudo mysql -e "CREATE DATABASE sg_property_scratch CHARACTER SET utf8mb4"
sudo mysql sg_property_scratch < singapore_property.sql
sudo mysql sg_property_scratch -N -r -e "SELECT JSON_OBJECT('slug', n.slug, 'asset_id', n.assetId, 'name', n.name, 'district', n.district,
  'developer', n.developer, 'property_type', n.propertyType, 'tenure', n.tenure, 'avg_psf', n.avgPsf, 'unit_sold_pct', n.unitSoldPct,
  'completion', n.completion, 'url', n.url, 'thumbnail', n.thumbnail, 'has_360', n.has360, 'lat', n.lat, 'lng', n.lng, 'is_active', n.isActive,
  'detail_at', n.detailAt, 'updated_at', n.updated_at, 'top_date', JSON_EXTRACT(n.raw, '$.top_date'), 'price', JSON_EXTRACT(n.detail, '$.price'),
  'overview', JSON_EXTRACT(n.detail, '$.overview'), 'photos', JSON_EXTRACT(n.detail, '$.photos'), 'unit_types', JSON_EXTRACT(n.detail, '$.unit_types'),
  'floorplans', JSON_EXTRACT(n.detail, '$.floorplans'), 'detail_source', JSON_UNQUOTE(JSON_EXTRACT(n.detail, '$.source')),
  'units', (SELECT JSON_ARRAYAGG(JSON_OBJECT('tower', u.tower, 'storey', u.storey, 'stack', u.stack, 'unit', u.unit, 'sqft', u.sqft,
    'bedrooms', u.bedrooms, 'status', u.status, 'txn_date', u.txnDate, 'psf', u.psf, 'price', u.price)) FROM ih_sg_units u WHERE u.projectSlug = n.slug))
  FROM ih_sg_newproj n ORDER BY n.id;" > sg_new_projects_YYYYMMDD.jsonl && gzip -k sg_new_projects_YYYYMMDD.jsonl
```

## Related files

- `database/migrations/catalogue/2026_10_14_100000_add_singapore_to_countries.php`,
  `database/migrations/2026_10_14_100001_attach_singapore_to_market_sites.php`,
  `database/migrations/catalogue/2026_10_14_100002_seed_singapore_providers.php`
- `config/markets.php` (`SG`), `config/project_catalogue.php` (`edgeprop-sg`, `ura`, the SG waivers)
- `app/Support/SgMarketLedger.php`, `app/Support/SgDistricts.php`
- `app/Console/Commands/ImportSingaporeMarketLedger.php`, `StoreSingaporeNewProjectMedia.php`, `PublishSingaporeEstates.php`
- `app/Services/Property/Ingestion/Adapters/UraLedgerAdapter.php`, `SingaporeNewProjectsAdapter.php`, `SgUnitLayouts.php`
- `app/Services/Property/Scraping/SingaporeProjectNormalizer.php`, `app/Services/Property/SingaporeAssetFetcher.php`
- `app/Services/Property/CatalogueDetailService.php` (`PORTAL_LAUNCH_PROVIDERS`), `app/Actions/BuildNewProjectListing.php` (`portalLaunchScope`, `PRICE_BANDS_SGD`)
- `src/PropertyLab/Research/SgRecordedSales.php`, `ResearchMarket.php`, `CatalogueExplorerIndex.php`, `CatalogueExplorerEvidence.php`
- `resources/js/utils/propertylab/heatmapModel.js`, `resources/js/Pages/Main/Site/newProjects.js`, `Components/PropertyLab/Advisor/ExplorerPanel.vue`
- `scripts/sg-market-on-site.php`
- Tests: `tests/Unit/Ingestion/SgUnitLayoutsTest.php`, `tests/Unit/Scraping/SingaporeProjectNormalizerTest.php`,
  `tests/Feature/Property/SingaporeLaunchAccessTest.php`, `tests/Unit/Common/MarketProfileTest.php`
