CreateTO procurement (MERX) — one buyer profile covers CreateTO, Build Toronto and TPLC

**What it is**: the City's real estate agency (launched 2018-01-01), operationally consolidating two still-extant City corporations — Build Toronto and Toronto Port Lands Company — through service agreements (https://www.toronto.ca/city-government/accountability-operations-customer-service/city-administration/city-managers-office/agencies-corporations/agencies/createto/). Manages the City's ~$27B / 8,446-property portfolio. This one issue disposes of **three** triage rows: Build Toronto is a dormant shell ($3.02M total liabilities; even its statutory auditor is procured by the City, https://www.toronto.ca/legdocs/mmis/2025/ex/bgrd/backgroundfile-256164.pdf) and TPLC is a live landowner ($459.65M assets, 80+ tenants) with no procurement operation — both bodies' procurement **is** CreateTO's.

**Venue**: MERX. CreateTO's own page says it outright: "All current, open procurements can be viewed and responded to via MERX, the electronic tendering service used by CreateTO" (https://createto.ca/get-involved/procurement/, procurement@createto.ca), linking https://www.merx.com/public/solicitations/open?keywords=createto. The shared buyer profile is `merx.com/buildtorontotplc` — snippet title literally "MERX : CreateTO (Build Toronto, TPLC) - solicitations" — with six TPLC-named RFPs observed 2021-2026 (e.g. RFP#2024-010 landscaping, RFP#2026-017 open in 2026). **All MERX URLs snippet-confirmed only; never fetched, per #103.**

**Not in the feed**: 0 Client_Division rows for CreateTO/Build Toronto/TPLC across 7,657 solicitations. The single feed mention is itself the proof of venue: doc 0000283274 (Jack Layton Ferry Terminal, RFP#2024-036) is a cross-posted notice whose `Specific_Conditions` read "Issued by CreateTO on MERX. Interested parties to submit bid on MERX" with placeholder buyer fields — the City's own infrastructure naming the venue.

**Shape of the record**: RFSQ-established Approved Service Provider rosters plus open RFP/RFQ; roster call-ups will never surface as public postings, so the capturable record is the RFP/RFSQ layer (predominantly professional services — architectural, engineering, environmental, compliance). Own RFP numbering (`RFP#YYYY-NNN`), a fourth keyspace with no join to the 10-digit spine.

**Adapter implications**: MERX already serves TTC (#104), Police (#105), Parking Authority (#106); TPASC is also on MERX (low materiality, no issue — would ride along). A buyer-profile-scoped capture of `buildtorontotplc` is the target, not the keyword search (keyword matching misses TPLC-named postings that don't say "CreateTO").

**Open questions**: MERX terms of use (#103) gate everything; buyer-profile vs keyword capture; whether pre-2018 Build Toronto/TPLC legacy postings exist anywhere (out of scope for a forward capture); watch for Build Toronto's formal dissolution (contemplated, not enacted — AGM cycle continues).

Start with issue #103 on MERX terms and compare the existing MERX work for TTC (#104), Police (#105), and Parking Authority (#106). Confirm whether buyer-profile capture is permitted, then scope the CreateTO/Build Toronto/TPLC RFP and RFSQ records around the buildtorontotplc profile; done means the forward feed captures those records without relying on keyword matching.

Written by the indexing model from the issue text.