Python rewrite of the Urb/Homemaker stack
When the seed is an undivided bare plot (init.dom), auto-generate pop_size random topologies before the memetic loop starts, each evaluated at child_budget. This crosses the zero-feasibility region that single-seed chaining cannot escape — the programme-house cold start was stalling at 18 fails after 2000 evals vs urb-evolve's 6. Auto-detection via seed_root.divided preserves the existing single-seed path for warm starts from existing designs; all previous tests pass unchanged. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .beads | ||
| .claude | ||
| experiments | ||
| src/homemaker | ||
| tests | ||
| .gitignore | ||
| AGENTS.md | ||
| 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.