Act A — The Vacancy Nobody Could Find
Transitional housing in Canadian cities is not scarce in aggregate. It is scarce for specific people with specific needs.
A woman fleeing domestic violence who uses a rollator walker and has a child under ten needs a unit that is: wheelchair-accessible, in a building that the abusive partner doesn't know about, near a school with an available register, in a program that accepts children, with no male residents on the same floor, and close enough to transit that she can get to supervised access appointments without a car.
There are units in Hamilton that meet all of those criteria. On any given week, one or two of them are vacant. The caseworker who has this client does not know which ones. She calls the housing providers she knows personally. She doesn't know all of them. Three days of phone calls and one placement referral refused later, the client is still in the shelter.
The unit at the supportive housing program on the east side has been vacant for twenty-two days. The program coordinator updated her spreadsheet twice. Nobody called.
The following is a fictional account of how MarketForge closes this gap without compromising the safety or privacy of the people it serves.
Act B — The Story
Renata is an intake caseworker at a Hamilton women's shelter. She has a client — Maria, name changed — who arrived three days ago with her seven-year-old daughter. Maria uses a rollator walker due to a hip injury. She is fleeing a domestic violence situation and the abusive partner knows the addresses of three other shelters in the city. The placement criteria are specific: ground-floor accessible unit, no male residents on the floor, program does not share address with the public, close to a school, accepts children.
Renata registers Maria's need profile on the MarketForge housing platform with explicit, documented consent — including what data is shared, with whom, and for what purpose. The consent is recorded in the ConsentEvent log. Maria's name is not in the matching profile. The profile contains disability accommodation requirements, safety criteria, household composition, school-age child yes/no, and location constraints.
Diane coordinates a twelve-unit supportive housing program in Hamilton's east end. The program has three accessible ground-floor units. Unit 4 has been vacant for twenty-two days — the previous tenant moved to permanent housing last month. The unit meets the criteria: ground-floor accessible, women-only floor, program address not publicly listed, one block from a primary school.
Diane's program registered on the platform six weeks ago at the suggestion of the Hamilton Community Legal Clinic. Their unit profile encodes physical accessibility, gender composition, address disclosure policy, pet policy, children policy, and availability.
The platform matches Maria's anonymized need profile to Unit 4. The match is flagged as high-priority given the domestic violence safety criteria. Renata receives a structured match notification describing the unit's fit with each of Maria's requirements — no identifying information about the unit's address is included in the initial notification, consistent with the safety protocol.
The Generative Match Story generated for Renata describes how the placement would work: the referral process for Diane's program, the documentation required (shelter intake form, child's school registration, Ontario Works file number), the typical timeline from referral to move-in (three to five days), and the support services bundled with the unit (weekly case management, community group access, children's programming). It flags that the unit has a pet restriction — Renata's notes don't mention a pet, so this is noted as a clarifying question for the intake conversation.
Renata reads the scenario. Unit 4 is a strong match. She contacts Diane through the platform's secure messaging channel. The referral is initiated that afternoon.
Maria moves in four days later.
Act C — Why This Market Stays Broken Without Infrastructure
The housing system in Canadian cities has units, caseworkers, and clients. What it lacks is a shared information layer that connects unit capabilities and individual needs in real time, without requiring caseworkers to maintain personal networks across every provider in the city.
The matching knowledge that Renata needs — which units are accessible, which programs accept children, which providers don't share their address publicly — lives in twenty different spreadsheets maintained by twenty different housing providers. None of it is searchable. None of it updates in real time.
The consequence is not just inefficiency. It is harm: preventable returns to street homelessness, preventable shelter crowding, preventable trauma from placement into the wrong program. The units are there. The system cannot find them.
What thin market infrastructure does is create the shared information layer — with the consent architecture, the privacy safeguards, and the multi-channel access that a social services context requires.
Characters and cases are fictional. The housing programs, eligibility frameworks, and consent requirements described reflect real Canadian municipal housing system operations. DeeperPoint is building the infrastructure this story describes.