109849e438
Owner's ruling. Measured over the twelve baseline layouts as realised value per m2 (rate x quality, not the rate alone): as shipped before this room 67.0 terrace 294.6 violates, 4.39x value_supported=100 only room 67.0 terrace 98.2 violates, 1.46x geometric mean only room 132.9 terrace 296.8 violates, 2.23x both room 132.9 terrace 98.9 satisfies The 4.4x is roughly 2.2x aggregation and 2.0x rate, so neither half alone is enough. That is why 39.18's geometric-mean aggregation moves from default-OFF to default-ON here rather than waiting on its own A/B: it is not an optional improvement, it is half of a ruling. value_supported 300 -> 100, and set to value_outside rather than to a number that makes the inequality come out -- back-solving from the corpus's measured mean room quality would rot the moment either changed. Outdoor space is worth the same to an occupant whatever level it sits on; the real difference between a ground garden and a roof terrace is what it takes to BUILD, and cost already says that (outside 10.0 vs outside_supported 110.0). Value describes worth, cost describes structure, and the level belongs in the second. Changed in CONF_DEFAULTS and the four corpus patterns.config files, which all declared 300.0 explicitly. NOT changed in harbor-house-l0 (a shape-curve test fixture) or y51-sweep-* (historical fixtures that exist to reproduce past measurements) -- repricing those would destroy what they are for. Neither change can move a fail, structurally rather than luckily: value rates never enter fail emission, and evaluate_leaf emits each fail from its factor before anything is combined. Verified corpus-wide: identical fail sets, scores +11% to +169% (and -5% once, on a layout that is mostly terrace). tests/test_terrace_value_ruling.py pins the ruling as an invariant of the objective, and asserts that reverting the aggregation breaks it again, so neither half can be quietly dropped. The 500k cold-start baseline (39.12) is superseded -- this changes what "good" means. The layouts stay valid and their fail counts are unchanged, but a fresh corpus run is needed before any new number is compared with them. Still untouched: circulation returns 0.07 per unit cost against a room's 0.66, by far the worst thing a building can contain. That is homemaker-py-hxi. Refs homemaker-py-ecx. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB
107 lines
2 KiB
Text
107 lines
2 KiB
Text
---
|
|
# Example patterns.config for programme-driven building evolution
|
|
#
|
|
# This file demonstrates how to define a building programme within
|
|
# the standard patterns.config file format. The presence of the
|
|
# 'spaces' key automatically triggers programme-driven mode.
|
|
|
|
# Building programme: 2-bedroom house with ensuite
|
|
spaces:
|
|
b1:
|
|
usage: bedroom
|
|
name: Master Bedroom
|
|
size:
|
|
- 16.0
|
|
- 4.0
|
|
width:
|
|
- 4.0
|
|
- 1.0
|
|
proportion:
|
|
- 1.5
|
|
- 0.5
|
|
adjacency:
|
|
- c
|
|
t1:
|
|
usage: toilet
|
|
name: Ensuite Bathroom
|
|
size:
|
|
- 5.0
|
|
- 1.5
|
|
width:
|
|
- 2.5
|
|
- 0.5
|
|
adjacency:
|
|
- b1
|
|
b2:
|
|
usage: bedroom
|
|
name: Second Bedroom
|
|
size:
|
|
- 12.0
|
|
- 3.0
|
|
width:
|
|
- 3.5
|
|
- 0.8
|
|
adjacency:
|
|
- c
|
|
t2:
|
|
usage: toilet
|
|
name: Guest Bathroom
|
|
size:
|
|
- 4.0
|
|
- 1.5
|
|
adjacency:
|
|
- c
|
|
l1:
|
|
usage: living
|
|
name: Living/Dining/Kitchen
|
|
size:
|
|
- 35.0
|
|
- 8.0
|
|
width:
|
|
- 4.5
|
|
- 1.0
|
|
proportion:
|
|
- 2.0
|
|
- 0.8
|
|
level: 0
|
|
adjacency:
|
|
- c
|
|
t3:
|
|
usage: toilet
|
|
name: Ground Floor WC
|
|
size:
|
|
- 3.0
|
|
- 1.0
|
|
adjacency:
|
|
- c
|
|
level: 0
|
|
|
|
# Building constraints
|
|
storey_minimum: 2
|
|
storey_limit: 5
|
|
force_roof_garden: 0
|
|
|
|
# Circulation ratio (penalise excessive corridors)
|
|
ratio_circulation:
|
|
- 0.00
|
|
- 0.15
|
|
|
|
# Outside space ratio
|
|
ratio_outside:
|
|
- 0.30
|
|
- 0.15
|
|
|
|
# Staircase requirements
|
|
staircase_min: 1
|
|
staircase_max: 1
|
|
|
|
# Other standard parameters can be included
|
|
value_inside: 300.0
|
|
value_circulation: 50.0
|
|
value_outside: 100.0
|
|
# homemaker-py-ecx (DESIGN.md §39.19): an upper-level terrace is worth what
|
|
# outdoor space is worth (value_outside); it is the COST that differs by level
|
|
# (outside 10.0 vs outside_supported 110.0), not the value. At 300.0 -- the
|
|
# `value_inside` rate -- a terrace was worth more per square metre than a real
|
|
# internal room, which the owner ruled out.
|
|
value_supported: 100.0
|