Python rewrite of the Urb/Homemaker stack
Bruno Postle
7fccc05c0d
Self-contained design + plan structured for breaking into bd (beads) tasks: domain constraints that fix the slicing representation; what was built; full empirical record (geometry port validated 35/35; area-proxy solver falsified; perpendicular artifact resolved via equal-offset cuts; full-fitness frozen-topology optimisation validated with 24-67% headroom; 0.5^n cliff); validated memetic architecture; component plan; phased roadmap; risks/open questions; repro steps; gotchas. Oracle throughput measured: ~0.99s/dom batched vs 1.65s single (assessment- dominated). urb-fitness.pl batches many doms per call, so native fitness is a later speed/scale optimisation, not a gate; favour population/batch optimisers and prototype the search on the batched oracle first. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| experiments | ||
| src/homemaker | ||
| .gitignore | ||
| CLAUDE.md | ||
| DESIGN.md | ||
| pyproject.toml | ||
| README.md | ||
homemaker-py
Programme-driven building-layout search over slicing trees. A clean-room Python successor to the Perl Urb project, intended to eventually be 100% Python.
Why a rewrite
Urb represents a building as a binary slicing tree where room sizes are derived top-down from division ratios. That makes room area an emergent property of every cut above it, which:
- gives the genome low locality (a cut near the root rescales every descendant),
- makes target room sizes nearly impossible to hit, so the gaussian size penalty dominates fitness, and
- defeats crossover (transplanted subtrees lose their proportions).
homemaker inverts this: leaves carry target dimensions from the programme and division ratios are solved bottom-up for a fixed topology. The evolutionary search then only explores topology + types + adjacency.
Phase plan
- Solver experiment (current): port Urb's geometry, re-solve ratios from programme targets, score the result against the original via the Perl oracle.
- Native Python fitness (retire the Perl oracle).
- Canonical slicing encoding (normalized Polish expression) + memetic search.
Layout
src/homemaker/dom.py— read/write Urb.domYAML into aNodetree.src/homemaker/geometry.py— faithful port of Urb's top-down geometry.src/homemaker/programme.py— parsepatterns.configspace requirements.src/homemaker/solver.py— bottom-up ratio solve (scipy).src/homemaker/oracle.py— Phase-1 scaffold: score a.domvia Urb'surb-fitness.pl.
The Perl oracle is the only throwaway component; everything else is permanent.