Hazard, pollution and climate as design constraints rather than events — planning for the conditions a district meets once and remembers for a decade.
10 May 2027
The argument#
Hazard, pollution and climate are not events that happen to a finished district — they are load cases the district is designed against from the first road, and every metre of protection is bought with rate base or with livability somewhere else.
What you will learn#
- Distinguish a hazard from an event: name, for one district, the human use system whose exposure turns a rainfall figure into a loss.
- Read the ground pollution, air pollution, noise, water and fire-hazard info views as a layered suitability analysis rather than as five separate warnings.
- Size a network for its worst week rather than its median week, and state the annual cost of the difference.
- Argue the case for withdrawing land from development, in rate-base arithmetic, without appealing to precaution alone.
Theory into practice#
- Ian Burton, Robert Kates and Gilbert F. White, The Environment as Hazard (1978). A hazard is the interaction of a natural event with a human use system; the event alone is only weather.
- Gilbert F. White, Human Adjustment to Floods (1945), with Raymond Burby’s “safe development paradox” (2006). Structural protection reduces frequent loss and increases the loss when protection is exceeded, because it invites occupation of the protected ground — written about flood levees, this week runs the same mechanism on fire defences.
- C. S. Holling, “Resilience and Stability of Ecological Systems” (Annual Review of Ecology and Systematics, 1973). Engineering resilience is return-to-normal speed; ecological resilience is how much disturbance a system absorbs before it flips to a different state.
- Ian McHarg, Design with Nature (1969). Layered suitability mapping — put development where the land can take it, established by stacking constraint layers before drawing anything.
- Charles Perrow, Normal Accidents (1984). Systems that are both interactively complex and tightly coupled fail in combinations nobody designed for.
The deck walks through where each of these lands, slide by slide, against the Thackray corridor’s fire load case.
Simulation mapping#
| Theory move | Cities: Skylines II mechanic | What students should watch happen |
|---|---|---|
| McHarg’s stacked constraint layers before siting | The ground pollution, air pollution, noise, water and fire-hazard info views, read in sequence over the same district | The five overlays disagree about where the good land is; the intersection of all five is much smaller than any one of them |
| Hazard as interaction, not event | The fire-hazard and electricity info views, with the wind overlay turned on inside the electricity view, read together against the Thackray corridor | Losses appear where the exposed corridor and zoning coincide, not just where the forest itself is densest |
| Downstream externality | Sewage outfall placement versus water-pumping-station intake placement on the same watercourse | Water pollution reaching the intake, health falling district-wide, and the outfall reading as “working” in its own tooltip throughout |
| Pollution as a decade-long condition | Ground pollution accumulation and its slow decay after the source is removed | The overlay stays stained for years after the industry closes, and the land value overlay stays low with it |
| Climate as a seasonal load case | Seasons and weather driving heating demand, water freezing, and solar and wind generation output | The same network passing in October and browning out in the second week of the coldest month |
| Perrow’s tight coupling | Week 7’s district-based service radii sharing one power and water trunk | A single generation shortfall taking water pumps offline, which takes fire response offline, inside one notification cluster |
Evidence standard. Named interface fields are direct readouts. Calculations shown from those fields are derived measures. Every fixed scenario value on this page is a worked hypothetical, not a captured run. See resources and evidence for access arrangements and worksheets.
The decision this week#
Fiscal performance against livability. The forced decision sits on the ridge flank of the Thackray corridor: the blocks that grew fastest around Thackray Cut’s western stops in Week 5, against the treeline on Verrall Ridge — the Week 1 rejected site, and the exact forest the studio’s load case begins a fire in.
Students must choose one of two moves before the studio session ends.
- Withdraw the ridge-flank land. Dezone it and hold the ground as a maintained firebreak. Livability rises — the exposure and its notification load disappear entirely. Fiscal performance falls: the corridor-edge rate revenue leaves the ledger, and the bus and pipe already built to serve it now serve nothing and still cost their upkeep.
- Defend the ridge-flank land. Clear a defensible perimeter, underground or reroute the power line, and add response capacity at Thackray Cut, then keep the blocks zoned. Fiscal performance holds. Livability holds at its current reading day to day. The exposure does not go away, it concentrates — and by White and Burby’s safe-development paradox, defended ground attracts higher-density redevelopment right up to the treeline, which is exactly the exposure the defence was meant to reduce.
There is no third option in which both metrics improve. Whichever they pick is a line in the capstone memo, and the jury will ask for the arithmetic.
Into the studio#
- Arrive with the Week 9 save and the fire-hazard and electricity views already checked over your own district, with the wind overlay on inside the electricity view, plus the Week 3 zoning drawing with the Pellow cells still industrial and the Week 7 reverse-salient card.
- The session reads the issued
d0,d3andd6checkpoints in order under the same 08:00 observation protocol — there is no 19-day live run. - Stack the fire-hazard view, the electricity view’s transmission lines and wind arrows, and the Thackray Cut geometry first, and draw what sits inside and outside the fire-response radius before opening any checkpoint.
- Finish by costing, in writing, whether to withdraw the ridge-flank land or defend it with access, power and response capacity. The build itself happens after this session, not during it.
Assessment connection#
Feeds the Comprehensive City Plan (Week 12, 50%, holistic) directly, and retrospectively strengthens Public Realm & Infrastructure Plan material already submitted in Week 9 — the firebreak-as-corridor-edge move is a livability argument and an infrastructure argument in the same drawing, which is the kind of double-duty the capstone rewards.
Nothing is assessed this week. What the capstone will be assessed on is whether the plan states its hazard exposure and prices it. A comprehensive plan that shows a district with no hazard section is read as a plan that did not open the overlays.
Teaching team
- Nadia Ilkhom — tutor