homemaker-layout/examples/maple-court/patterns.config
Claude a7ef9e2fa0
Remove ratio_circulation: the score is already a ratio
Owner: "I think a corridor could be worth a sixth of a room, this is ok. maybe
we should dump the ratio_circulation altogether if there is already a pressure
in circulation caused by the cost benefit ratio per msq. this is the kind of
thing we want to root out of the scoring model: anything that is double
counting, or using a gaussian where a linear ramp is appropriate, etc."

value_circulation = 50 stands; hxi's rate question is closed.

The duplication argument is stronger than it first looks. score = value/cost is
already a ratio, so the per-m2 economics (50 against a build cost of 200) is not
merely an absolute pressure -- adding corridor moves value/cost by an amount
that depends on how much of the building is already corridor. It is ALREADY
proportional. ratio_circulation said the same thing again as a whole-building
multiplier, on a curve where twice the corridor is far more than twice as bad.

Correction to my own first measurement: I overrode ratio_circulation and got
scores going DOWN when a <=1 multiplier was removed, which is impossible. All
four corpus programmes DECLARE ratio_circulation, so the CONF_DEFAULTS value I
had changed was never in play and the two arms differed only in sigma. Same
trap as value_supported in 39.19.

Against the keep-it case, recorded because it is the one real argument: three of
four declare a POSITIVE target (harbor/maple 0.08, health-centre 0.10), making
the term formally two-sided rather than "less is better". It does not survive
the numbers -- the lower side is worth at most 13.3% on the large programmes
against 99% on the upper side, and "a building needs some circulation" is
enforced structurally by access and connectivity, which no amount of value can
buy off.

Disabled in CONF_DEFAULTS and the four corpus configs, each with the reason
inline and a note that a [target, sigma] pair re-enables it. Fail sets
unchanged; it was always a value multiplier. Scores +42% to +7712%.

39.24 also sweeps every remaining term against the owner's two tests. Verdicts:
perpendicular, proportion, width, crinkliness, access, size's lower side,
ratio_outside, staircase volume and the count/limit fails are all sound.
Filed as homemaker-py-dpt: size's UPPER side (cost already charges area; 82% of
size fails are over-target), the minimum-internal-area factor (a third
statement of "build the rooms"), the 0.5**n_fails curve (a ruling, not a
measurement), and two dead paths -- ratio_public/private_outside, which no
config declares, and the daylight factor pinned to 1.0 since the descope.

Also updated a test I added last turn which asserted ratio_circulation was the
second charge; it now pins that the linear ramp is the ONLY one.

419 passed.

Closes homemaker-py-hxi.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB
2026-09-06 15:28:33 +00:00

436 lines
7.3 KiB
Text

---
# Maple Court - Larger-than-house benchmark (homemaker-py-leu.1, DESIGN.md §12.1)
#
# A three-storey assisted-living / co-housing facility. Built to be the first
# benchmark larger than harbor-house (16 programme entries): 26 distinct space
# entries / 52 room instances across 3 required storeys, with a harbor-like
# adjacency-to-c load and a handful of secondary adjacencies (k/da/o clusters).
#
# Code conventions (first letter is semantic in fitness.py): generic c/o/s are
# reserved for circulation / outside / sahn, so no ROOM code starts with c, o or
# s. Living-family rooms lead with l, kitchen k, dining d, bathroom t; everything
# else uses a neutral leading letter (default room scoring).
# Building programme: three-storey community living facility
spaces:
# ---- GROUND FLOOR (level 0): community + service ----
lr1:
usage: living
name: Common Living Room
size:
- 80.0
- 10.0
width:
- 6.0
- 1.5
proportion:
- 2.0
- 0.5
level: 0
adjacency:
- c
- o
ef1:
usage: none
name: Entrance Foyer
size:
- 15.0
- 3.0
width:
- 3.0
- 0.5
level: 0
adjacency:
- c
da1:
usage: living
name: Dining Area
size:
- 60.0
- 8.0
width:
- 5.0
- 1.0
proportion:
- 2.5
- 0.8
level: 0
adjacency:
- c
- k1
- o
k1:
usage: kitchen
name: Kitchen
size:
- 30.0
- 5.0
width:
- 4.0
- 1.0
level: 0
adjacency:
- da1
- c
ws1:
usage: living
name: Workshop Space
size:
- 40.0
- 6.0
width:
- 5.0
- 1.0
proportion:
- 1.8
- 0.5
level: 0
adjacency:
- c
- o
la1:
usage: utility
name: Laundry Room
size:
- 20.0
- 4.0
width:
- 3.0
- 0.8
level: 0
adjacency:
- c
me1:
crinkliness: none # no window needed
usage: utility
name: Mechanical/Electrical Room
size:
- 25.0
- 4.0
width:
- 3.5
- 0.8
level: 0
adjacency:
- c
ur1:
crinkliness: none # no window needed
usage: utility
name: Ground Floor Storage
size:
- 22.0
- 4.0
width:
- 3.0
- 0.8
level: 0
adjacency:
- c
rc1:
usage: none
name: Reception Office
size:
- 14.0
- 3.0
width:
- 3.0
- 0.6
level: 0
adjacency:
- c
ph1:
usage: bedroom
name: Clinic Room
size:
- 18.0
- 3.5
width:
- 3.0
- 0.6
level: 0
adjacency:
- c
gh1:
usage: living
name: Greenhouse
size:
- 24.0
- 4.0
width:
- 3.5
- 0.8
level: 0
adjacency:
- c
- o
# Meeting rooms - anonymous interchangeable (3 total, ground floor)
m:
usage: living
name: Meeting Room
size:
- 10.0
- 2.0
width:
- 2.5
- 0.5
level: 0
adjacency:
- c
count: 3
# Ground-floor bathrooms (6 total)
t:
usage: toilet
name: Bathroom
size:
- 6.0
- 1.5
width:
- 2.0
- 0.5
level: 0
adjacency:
- c
count: 6
# ---- FIRST FLOOR (level 1): residents' shared + neighborhoods ----
li1:
usage: living
name: Library Corner
size:
- 20.0
- 4.0
width:
- 3.5
- 0.8
level: 1
adjacency:
- c
lo1:
usage: living
name: Lounge
size:
- 30.0
- 5.0
width:
- 4.0
- 1.0
proportion:
- 2.0
- 0.6
level: 1
adjacency:
- c
- o
# Staff offices - anonymous (2 total)
em:
usage: bedroom
name: Staff Office
size:
- 12.5
- 2.5
width:
- 2.5
- 0.5
level: 1
adjacency:
- c
count: 2
# Sleeping neighborhoods - anonymous interchangeable (4 total)
n:
usage: bedroom
name: Neighborhood
size:
- 60.0
- 8.0
width:
- 5.0
- 1.0
proportion:
- 2.0
- 0.6
level: 1
adjacency:
- c
count: 4
ur2:
crinkliness: none # no window needed
usage: utility
name: First Floor Storage
size:
- 18.0
- 3.5
width:
- 3.0
- 0.8
level: 1
adjacency:
- c
en1:
usage: living
name: TV / Media Room
size:
- 22.0
- 4.0
width:
- 3.5
- 0.8
level: 1
adjacency:
- c
# Therapy rooms - anonymous (2 total)
py:
usage: bedroom
name: Therapy Room
size:
- 16.0
- 3.0
width:
- 3.0
- 0.6
level: 1
adjacency:
- c
count: 2
# ---- SECOND FLOOR (level 2): individual rooms + amenity ----
# Individual resident rooms - anonymous (12 total)
r:
usage: bedroom
name: Individual Room
size:
- 10.0
- 2.0
width:
- 2.5
- 0.5
level: 2
adjacency:
- c
count: 12
gy1:
usage: living
name: Exercise Room
size:
- 28.0
- 5.0
width:
- 4.0
- 0.8
proportion:
- 1.8
- 0.5
level: 2
adjacency:
- c
- o
ut1:
crinkliness: none # no window needed
usage: utility
name: Utilities Closet
size:
- 14.0
- 3.0
width:
- 2.5
- 0.6
level: 2
adjacency:
- c
ur3:
crinkliness: none # no window needed
usage: utility
name: Second Floor Storage
size:
- 16.0
- 3.0
width:
- 3.0
- 0.8
level: 2
adjacency:
- c
# Second-floor bathrooms (4 total)
tt:
usage: toilet
name: Upper Bathroom
size:
- 6.0
- 1.5
width:
- 2.0
- 0.5
level: 2
adjacency:
- c
- r # Brand: a WC beside sleeping space can be knocked through later
count: 4
q1:
usage: bedroom
name: Quiet Room
size:
- 12.0
- 2.5
width:
- 2.5
- 0.6
level: 2
adjacency:
- c
# Building constraints
storey_minimum: 3
storey_limit: 4
force_roof_garden: 0
# Circulation ratio (allow more circulation for larger building)
# homemaker-py-hxi (DESIGN.md §39.24): disabled. The score is value/cost, a
# ratio, so the per-m2 economics (circulation worth 50 against a build cost of
# 200) is ALREADY a proportional pressure against circulation -- this said the
# same thing a second time, and with a curve where twice the corridor is far
# more than twice as bad. Its other side, "a building needs some circulation",
# was worth at most 13% here and is enforced structurally anyway by the access
# and connectivity checks. Set a [target, sigma] pair to re-enable.
ratio_circulation:
# Outside space ratio (courtyard requirement)
ratio_outside:
- 0.15
- 0.10
# Staircase requirements (main + secondary)
staircase_min: 2
staircase_max: 2
# Economic parameters
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