Bruno Postle
479d4a57d5
Leaf-sharing evolve runs optimised a sharing-credited objective (a shared leaf of code X with share=k counts as k programme rooms, size re-centred on k*target) but wrote the un-materialised genome, which the canonical homemaker-fitness rates catastrophically worse (harbor-house: internal 1.03e-05 vs canonical 6.73e-29, 15 critical missing-room fails). Fix: before write, driver.polish_finish() unfolds every live shared leaf into k distinct rooms (operators.unfold_shared_leaves — pays down the count deficit) then warm-starts a leaf_sharing=False polish search from the unfolded genome so the materialised rooms get proportion/width/size cleanup. Returned best.fitness is the canonical score (leaf_sharing off => internal == canonical). This is yaa's proven unfold-then-polish path, made automatic. evolve.py: new --polish-budget (env HOMEMAKER_POLISH_BUDGET; -1=auto= budget//2, 0=unfold+rescore only). Interrupt forces polish_budget=0 for a fast honest output. Default stays --leaf-sharing on (its topology-search speed retained; output made honest by the finish). Schedule B in-run annealing remains homemaker-py-kpu. Verified (harbor-house 3000+1500): reported polish fitness 4.79788e-27 matches canonical homemaker-fitness exactly, 0 critical fails. Tests: 254 pass (+3 polish_finish). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M8566xAxTnwtJTkpXjYNZm |
||
|---|---|---|
| .. | ||
| hooks | ||
| .gitignore | ||
| config.yaml | ||
| issues.jsonl | ||
| metadata.json | ||
| README.md | ||
Beads - AI-Native Issue Tracking
Welcome to Beads! This repository uses Beads for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
What is Beads?
Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
Learn more: github.com/steveyegge/beads
Quick Start
Essential Commands
# Create new issues
bd create "Add user authentication"
# View all issues
bd list
# View issue details
bd show <issue-id>
# Update issue status
bd update <issue-id> --claim
bd update <issue-id> --status done
# Sync with Dolt remote
bd dolt push
Working with Issues
Issues in Beads are:
- Git-native: Stored in Dolt database with version control and branching
- AI-friendly: CLI-first design works perfectly with AI coding agents
- Branch-aware: Issues can follow your branch workflow
- Always in sync: Auto-syncs with your commits
Why Beads?
✨ AI-Native Design
- Built specifically for AI-assisted development workflows
- CLI-first interface works seamlessly with AI coding agents
- No context switching to web UIs
🚀 Developer Focused
- Issues live in your repo, right next to your code
- Works offline, syncs when you push
- Fast, lightweight, and stays out of your way
🔧 Git Integration
- Automatic sync with git commits
- Branch-aware issue tracking
- Dolt-native three-way merge resolution
Get Started with Beads
Try Beads in your own projects:
# Install Beads
curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
# Initialize in your repo
bd init
# Create your first issue
bd create "Try out Beads"
Learn More
- Documentation: github.com/steveyegge/beads/docs
- Quick Start Guide: Run
bd quickstart - Examples: github.com/steveyegge/beads/examples
Beads: Issue tracking that moves at the speed of thought ⚡