Week 10 Studio: Hazard Scenario

Stress-test the district against a hazard it was never designed for, and separate what failed from what merely looked alarming.

10 May 2027

Before you come#

Bring <student ID>-w09 exactly as submitted, together with last week’s trend readings. Check the fire-hazard and electricity views over your district, and read wind off the arrows inside the electricity view — there is no wind view to open on its own. Bring the Week 3 zoning drawing with the Pellow cells still industrial, the Week 7 reverse-salient card and the unfunded treatment line.

Have the issued kerrow-ref-w10-d0, -d3, -d6 and -recovered checkpoints available. Before opening any of them, branch the personal district as <student ID>-w10. That branch is your Week 10 record and the file Week 11 opens; nothing you load this afternoon becomes it. There is no 19-day live run.

The load case#

The supported load case is a forest fire beginning on forested Verrall Ridge, the Week 1 rejected site. It tests the only westward gradient at Thackray Cut, power transmission and the remaining fire-response radius. The checkpoints were recorded on the design-lab build and are read as staged reference evidence. This is not a flood or a water-source editor trick.

Ombersley remains industrial ground. Smoke and downwind load are read against the Pellow cells as industry, not against a reference housing conversion. If a student’s own save contains housing there, that is evidence about that save, not a replacement for the common scenario.

The three hours#

Begin by stacking the fire-hazard view, the electricity view’s transmission lines and wind arrows, and the Thackray Cut geometry. Draw the fire-exposed land and count what sits inside and outside the response radius. Then load d0, d3 and d6 in order and use the same 08:00 observation protocol on each.

In the reference sequence, Thackray Cut is closed for four in-game days and peak travel reaches 13.6 minutes against Week 9’s 11.1-minute trend. The d3 electricity availability bar shows the power shortfall, and the fire-coverage view shows the coupled response limit. Keep those as two fields. District-wide happiness troughs at 41% on d3, including in blocks that did not burn. The event month closes at −₡14,200, not a continuing monthly rate.

At 14:40, load -recovered. No intervention is inserted between d6 and the recovery trace. Read it against d3, then close it without saving. The fire ran on the issued district, not on yours, so your own save leaves this afternoon exactly as it arrived: what Week 10 produces is the paper, not a changed district.

Finish with two board columns and then cost, in writing, whether to withdraw fire-exposed land or defend it with access, power and response capacity. Do not build that choice this afternoon.

Broke, or looked alarming#

What broke: ridge access, power transmission and fire response. Each entry names the view, reading and checkpoint that supports it. These failures connect to siting and network decisions made in Weeks 1, 3 and 7.

What looked alarming: the happiness trough and notification cluster. Both resolve on the recovered checkpoint without a design move. That does not make them false; it makes them event readings rather than evidence of the district’s settled state.

Withdraw exposed land and lose rate base. Defend it and carry the exposure plus the cost of oversizing. The trade is fiscal performance against livability. There is no branch in which both improve.

The quoting rule#

Event ≠ trend. A later claim never says “happiness was 41%” on its own. It says “41% on kerrow-ref-w10-d3” and sets that against -recovered. Keep the land-value row blank this week; Week 11 plots Week 9 to Week 11 with the gap dashed.

Leave with <student ID>-w10, branched from your own district before any checkpoint was opened, the two-column fault sheet, three named screenshots and the costed exposure statement. Copy the save off-machine and upload the record by 21:00.