homemaker-layout/experiments/results/ab_ssz_power.csv

programme,seed,mode,urb_hard,urb_soft,urb_total,own_hard,own_soft,own_total,elapsed_s
harbor-house,0,urb,16,39,55,16,39,55,76.4
harbor-house,1,urb,22,45,67,22,45,67,80.8
harbor-house,2,urb,22,40,62,22,40,62,76.6
harbor-house,3,urb,15,48,63,15,48,63,75.2
harbor-house,4,urb,17,42,59,17,42,59,83.9
harbor-house,5,urb,29,42,71,29,42,71,81.7
ssz: 61% of reported crinkliness fails are not defects; two corrections Correction 1: 38.8's A/B scores every arm under stock urb, which is only sound if stock is ground truth -- and stock is what this section shows is miscalibrated. Scoring the repair under the objective it repairs penalises it for repairing. That result is not evidence against usage_daylight. The measurement that matters needs no search: are the emitted failures true? audit_crinkliness_truth.py classifies every stock crinkliness fail by the leaf's declared usage. 164 of 271 (61%) are reported against spaces that want no daylight -- stores, WCs, plant, corridors, covered courtyards -- and it holds on evolved artefacts (maple generated.dom: 64%), not just constructed seeds. Under value = 0.5 * len(failures) each one halves the fitness of a design that did nothing wrong. Correction 2: usage: is the wrong key, and usage_daylight as written mis-keys it. 39.7 established usage: as an ACCESS-requirement class. "Needs no special access" and "needs no window" are different questions, and the corpus separates them: usage: none is Waiting Room, Reception, Reception Office, Entrance Foyer -- a waiting room plainly wants daylight and DAYLIGHT_USAGES exempts it. The usage: bedroom half is right, but by luck of where the access axis happened to fall. The audit is robust to that error (61% -> 57% if none is reclassified), so the finding stands; the design does not. Daylight needs its own declared per-space axis, decided by the programme author as usage: was. usage_daylight stays default off and is not the shipping fix. The compact-side clip is the right shape for the factor, so the mechanism is retained pending a daylight: attribute to key it on. Higher-power A/B stopped: it was chasing a score against a flawed objective with a mis-keyed fix. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB 2026-08-26 18:07:01 +00:00			`programme,seed,mode,urb_hard,urb_soft,urb_total,own_hard,own_soft,own_total,elapsed_s`
			`harbor-house,0,urb,16,39,55,16,39,55,76.4`
			`harbor-house,1,urb,22,45,67,22,45,67,80.8`
			`harbor-house,2,urb,22,40,62,22,40,62,76.6`
			`harbor-house,3,urb,15,48,63,15,48,63,75.2`
			`harbor-house,4,urb,17,42,59,17,42,59,83.9`
			`harbor-house,5,urb,29,42,71,29,42,71,81.7`