Fix mutate_level_add: use generic C/O floor instead of room duplicate
Previously level_add copied the top storey exactly, duplicating all
named programme rooms and immediately triggering space-count failures
for every room on the new floor. The lex outer-search comparison
(-n_fails, score) then always rejected the multi-storey child because
its fail count was far higher than the single-storey parent.
Fix: retype all named-room leaves on the new storey to generic C or O
before admitting the child. The outer search then retypes them
incrementally via the normal retype operator. This allows level_add to
produce designs with the same fail count as the parent (storey_minimum
fail removed, no duplication fails added), making the multi-storey
transition visible to the lex selector.
Result on programme-house cold start (init.dom, 100k evals, 4 workers):
before: 6 fails, single-storey, stuck after 40k evals
after: 4 fails, two-storey, still improving at 100k
Also adds examples/harbor-house/ from urb/examples for future runs.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-14 10:33:05 +01:00
|
|
|
node:
|
|
|
|
|
- - 0.0
|
|
|
|
|
- 0.0
|
|
|
|
|
- - 25.0
|
|
|
|
|
- 2.0
|
|
|
|
|
- - 23.0
|
|
|
|
|
- 31.0
|
|
|
|
|
- - 0.0
|
|
|
|
|
- 31.0
|
|
|
|
|
perimeter:
|
|
|
|
|
a: private
|
|
|
|
|
b: private
|
|
|
|
|
c: null
|
|
|
|
|
d: null
|
|
|
|
|
rotation: 0
|
|
|
|
|
division:
|
|
|
|
|
- 0.5206890368316089
|
|
|
|
|
- 0.5206890368316089
|
|
|
|
|
height: 3.0
|
|
|
|
|
elevation: 0.0
|
|
|
|
|
wall_inner: 0.08
|
|
|
|
|
wall_outer: 0.25
|
|
|
|
|
l:
|
|
|
|
|
rotation: 1
|
|
|
|
|
division:
|
|
|
|
|
- 0.4900271770215713
|
|
|
|
|
- 0.4900271770215713
|
|
|
|
|
l:
|
|
|
|
|
rotation: 2
|
|
|
|
|
division:
|
|
|
|
|
- 0.28955830710300473
|
|
|
|
|
- 0.28955830710300473
|
|
|
|
|
l:
|
|
|
|
|
rotation: 1
|
|
|
|
|
division:
|
|
|
|
|
- 0.5900577549923657
|
|
|
|
|
- 0.5900577549923657
|
|
|
|
|
l:
|
|
|
|
|
rotation: 0
|
|
|
|
|
division:
|
|
|
|
|
- 0.5042565018475718
|
|
|
|
|
- 0.5042565018475718
|
|
|
|
|
l:
|
ju3: reject programme codes colliding with the c/o/s generic type prefixes
Closes homemaker-py-ju3. DESIGN.md §39.3.
The class: key from the bead's design was deliberately NOT built. Auditing
every use of the prefix rule first showed it runs deeper than c/o/s -- l/k/b/t
carry real adjacency semantics (graph.py builds bedroom<->toilet and
kitchen<->living relations from first characters) -- so re-plumbing the type
system would invalidate the whole corpus and every baseline, for a problem
whose damage is the silence, not the convention. Two findings made the smaller
fix sufficient: no corpus programme has ever declared a bare c/o/s code, so
check_space_counts' skip only ever discarded declared rooms; and nothing
references harbor's four codes in any adjacency or co_locate list.
- programme.validate_codes raises on a reserved-prefix code, with the full
explanation. Called from BOTH parse paths (programme._parse_spaces and
fitness.Fitness._load_programme parse conf["spaces"] independently, so
validating one would leave the other door open). l/k/b/t stay unreserved.
- harbor-house and harbor-house-l0 renamed: cr1->fr1, of->ao, st1->gs1,
st2->gs2. New prefixes are unused in harbor and semantically neutral, and
the two storage codes still share a prefix, preserving the structure
evaluate_building's per-code plot-ratio term depends on. name: unchanged.
- experiments/migrate_ju3_rename.py migrates .dom files written before the
rename (--check dry-runs). Pre-rename artefacts, notably evolved-3M*.dom,
must be migrated or their leaves read as unmatched generics.
- test_collapse_global's c/o/s exclusion test now uses a generic C leaf, which
is what the exclusion is actually for; it previously relied on a programme
code colliding, which is no longer possible.
Re-baseline (seed 1, 20k evals, same settings as §38's run): 57 fails against
the 32-instance effective programme -> 55 against the real 37-instance one,
with all five previously-lost room instances now placed inside their declared
sigma bands (fr1 87.2 vs declared 80, was 32.9/17.1; ao/gs1/gs2 were absent
entirely) and no failure naming any of the four codes. At one seed each,
57 vs 55 is within noise -- the robust result is the room placement, not the
count. Historical harbor numbers are not comparable to post-ju3 ones; filed
homemaker-py-t3s to restate 2v1's acceptance figure once evolved-3M is
migrated.
346 passed (+10 new), same 7 pre-existing fixture failures.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB
2026-08-26 09:06:08 +00:00
|
|
|
type: gs2
|
Fix mutate_level_add: use generic C/O floor instead of room duplicate
Previously level_add copied the top storey exactly, duplicating all
named programme rooms and immediately triggering space-count failures
for every room on the new floor. The lex outer-search comparison
(-n_fails, score) then always rejected the multi-storey child because
its fail count was far higher than the single-storey parent.
Fix: retype all named-room leaves on the new storey to generic C or O
before admitting the child. The outer search then retypes them
incrementally via the normal retype operator. This allows level_add to
produce designs with the same fail count as the parent (storey_minimum
fail removed, no duplication fails added), making the multi-storey
transition visible to the lex selector.
Result on programme-house cold start (init.dom, 100k evals, 4 workers):
before: 6 fails, single-storey, stuck after 40k evals
after: 4 fails, two-storey, still improving at 100k
Also adds examples/harbor-house/ from urb/examples for future runs.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-14 10:33:05 +01:00
|
|
|
rotation: 0
|
|
|
|
|
r:
|
ju3: reject programme codes colliding with the c/o/s generic type prefixes
Closes homemaker-py-ju3. DESIGN.md §39.3.
The class: key from the bead's design was deliberately NOT built. Auditing
every use of the prefix rule first showed it runs deeper than c/o/s -- l/k/b/t
carry real adjacency semantics (graph.py builds bedroom<->toilet and
kitchen<->living relations from first characters) -- so re-plumbing the type
system would invalidate the whole corpus and every baseline, for a problem
whose damage is the silence, not the convention. Two findings made the smaller
fix sufficient: no corpus programme has ever declared a bare c/o/s code, so
check_space_counts' skip only ever discarded declared rooms; and nothing
references harbor's four codes in any adjacency or co_locate list.
- programme.validate_codes raises on a reserved-prefix code, with the full
explanation. Called from BOTH parse paths (programme._parse_spaces and
fitness.Fitness._load_programme parse conf["spaces"] independently, so
validating one would leave the other door open). l/k/b/t stay unreserved.
- harbor-house and harbor-house-l0 renamed: cr1->fr1, of->ao, st1->gs1,
st2->gs2. New prefixes are unused in harbor and semantically neutral, and
the two storage codes still share a prefix, preserving the structure
evaluate_building's per-code plot-ratio term depends on. name: unchanged.
- experiments/migrate_ju3_rename.py migrates .dom files written before the
rename (--check dry-runs). Pre-rename artefacts, notably evolved-3M*.dom,
must be migrated or their leaves read as unmatched generics.
- test_collapse_global's c/o/s exclusion test now uses a generic C leaf, which
is what the exclusion is actually for; it previously relied on a programme
code colliding, which is no longer possible.
Re-baseline (seed 1, 20k evals, same settings as §38's run): 57 fails against
the 32-instance effective programme -> 55 against the real 37-instance one,
with all five previously-lost room instances now placed inside their declared
sigma bands (fr1 87.2 vs declared 80, was 32.9/17.1; ao/gs1/gs2 were absent
entirely) and no failure naming any of the four codes. At one seed each,
57 vs 55 is within noise -- the robust result is the room placement, not the
count. Historical harbor numbers are not comparable to post-ju3 ones; filed
homemaker-py-t3s to restate 2v1's acceptance figure once evolved-3M is
migrated.
346 passed (+10 new), same 7 pre-existing fixture failures.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB
2026-08-26 09:06:08 +00:00
|
|
|
type: gs1
|
Fix mutate_level_add: use generic C/O floor instead of room duplicate
Previously level_add copied the top storey exactly, duplicating all
named programme rooms and immediately triggering space-count failures
for every room on the new floor. The lex outer-search comparison
(-n_fails, score) then always rejected the multi-storey child because
its fail count was far higher than the single-storey parent.
Fix: retype all named-room leaves on the new storey to generic C or O
before admitting the child. The outer search then retypes them
incrementally via the normal retype operator. This allows level_add to
produce designs with the same fail count as the parent (storey_minimum
fail removed, no duplication fails added), making the multi-storey
transition visible to the lex selector.
Result on programme-house cold start (init.dom, 100k evals, 4 workers):
before: 6 fails, single-storey, stuck after 40k evals
after: 4 fails, two-storey, still improving at 100k
Also adds examples/harbor-house/ from urb/examples for future runs.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-14 10:33:05 +01:00
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
rotation: 1
|
|
|
|
|
division:
|
|
|
|
|
- 0.5042565018475718
|
|
|
|
|
- 0.5042565018475718
|
|
|
|
|
l:
|
|
|
|
|
type: O
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
type: ut1
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
rotation: 2
|
|
|
|
|
division:
|
|
|
|
|
- 0.5254855092815014
|
|
|
|
|
- 0.5254855092815014
|
|
|
|
|
l:
|
|
|
|
|
rotation: 1
|
|
|
|
|
division:
|
|
|
|
|
- 0.7453088885860744
|
|
|
|
|
- 0.7453088885860744
|
|
|
|
|
l:
|
|
|
|
|
rotation: 2
|
|
|
|
|
division:
|
|
|
|
|
- 0.5622884610865619
|
|
|
|
|
- 0.5622884610865619
|
|
|
|
|
l:
|
|
|
|
|
type: k1
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
rotation: 3
|
|
|
|
|
division:
|
|
|
|
|
- 0.545507016217933
|
|
|
|
|
- 0.545507016217933
|
|
|
|
|
l:
|
|
|
|
|
type: ws1
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
ju3: reject programme codes colliding with the c/o/s generic type prefixes
Closes homemaker-py-ju3. DESIGN.md §39.3.
The class: key from the bead's design was deliberately NOT built. Auditing
every use of the prefix rule first showed it runs deeper than c/o/s -- l/k/b/t
carry real adjacency semantics (graph.py builds bedroom<->toilet and
kitchen<->living relations from first characters) -- so re-plumbing the type
system would invalidate the whole corpus and every baseline, for a problem
whose damage is the silence, not the convention. Two findings made the smaller
fix sufficient: no corpus programme has ever declared a bare c/o/s code, so
check_space_counts' skip only ever discarded declared rooms; and nothing
references harbor's four codes in any adjacency or co_locate list.
- programme.validate_codes raises on a reserved-prefix code, with the full
explanation. Called from BOTH parse paths (programme._parse_spaces and
fitness.Fitness._load_programme parse conf["spaces"] independently, so
validating one would leave the other door open). l/k/b/t stay unreserved.
- harbor-house and harbor-house-l0 renamed: cr1->fr1, of->ao, st1->gs1,
st2->gs2. New prefixes are unused in harbor and semantically neutral, and
the two storage codes still share a prefix, preserving the structure
evaluate_building's per-code plot-ratio term depends on. name: unchanged.
- experiments/migrate_ju3_rename.py migrates .dom files written before the
rename (--check dry-runs). Pre-rename artefacts, notably evolved-3M*.dom,
must be migrated or their leaves read as unmatched generics.
- test_collapse_global's c/o/s exclusion test now uses a generic C leaf, which
is what the exclusion is actually for; it previously relied on a programme
code colliding, which is no longer possible.
Re-baseline (seed 1, 20k evals, same settings as §38's run): 57 fails against
the 32-instance effective programme -> 55 against the real 37-instance one,
with all five previously-lost room instances now placed inside their declared
sigma bands (fr1 87.2 vs declared 80, was 32.9/17.1; ao/gs1/gs2 were absent
entirely) and no failure naming any of the four codes. At one seed each,
57 vs 55 is within noise -- the robust result is the room placement, not the
count. Historical harbor numbers are not comparable to post-ju3 ones; filed
homemaker-py-t3s to restate 2v1's acceptance figure once evolved-3M is
migrated.
346 passed (+10 new), same 7 pre-existing fixture failures.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB
2026-08-26 09:06:08 +00:00
|
|
|
type: fr1
|
Fix mutate_level_add: use generic C/O floor instead of room duplicate
Previously level_add copied the top storey exactly, duplicating all
named programme rooms and immediately triggering space-count failures
for every room on the new floor. The lex outer-search comparison
(-n_fails, score) then always rejected the multi-storey child because
its fail count was far higher than the single-storey parent.
Fix: retype all named-room leaves on the new storey to generic C or O
before admitting the child. The outer search then retypes them
incrementally via the normal retype operator. This allows level_add to
produce designs with the same fail count as the parent (storey_minimum
fail removed, no duplication fails added), making the multi-storey
transition visible to the lex selector.
Result on programme-house cold start (init.dom, 100k evals, 4 workers):
before: 6 fails, single-storey, stuck after 40k evals
after: 4 fails, two-storey, still improving at 100k
Also adds examples/harbor-house/ from urb/examples for future runs.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-14 10:33:05 +01:00
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
type: O
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
type: da1
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
rotation: 2
|
|
|
|
|
division:
|
|
|
|
|
- 0.5017908930114854
|
|
|
|
|
- 0.5017908930114854
|
|
|
|
|
l:
|
|
|
|
|
type: r
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
type: li1
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
rotation: 0
|
|
|
|
|
division:
|
|
|
|
|
- 0.4006976137653344
|
|
|
|
|
- 0.4006976137653344
|
|
|
|
|
l:
|
|
|
|
|
rotation: 3
|
|
|
|
|
division:
|
|
|
|
|
- 0.48703066466032097
|
|
|
|
|
- 0.48703066466032097
|
|
|
|
|
l:
|
|
|
|
|
rotation: 2
|
|
|
|
|
division:
|
|
|
|
|
- 0.5562346554544078
|
|
|
|
|
- 0.5562346554544078
|
|
|
|
|
l:
|
|
|
|
|
type: m
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
rotation: 2
|
|
|
|
|
division:
|
|
|
|
|
- 0.5042565018475718
|
|
|
|
|
- 0.5042565018475718
|
|
|
|
|
l:
|
|
|
|
|
type: me1
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
type: C
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
rotation: 2
|
|
|
|
|
division:
|
|
|
|
|
- 0.6464404401824229
|
|
|
|
|
- 0.6464404401824229
|
|
|
|
|
l:
|
|
|
|
|
type: O
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
type: t
|
|
|
|
|
rotation: 0
|
|
|
|
|
r:
|
|
|
|
|
type: r
|
|
|
|
|
rotation: 3
|