df84bfe1e6
check_space_counts emitted, per missing room instance, two base failures plus one placeholder for each optional key the author happened to type -- has_size/has_width/has_proportion are literally "size" in c from the YAML. So a missing room cost 3, 4 or 5 fails depending on nothing but how verbosely its space was written, and under value *= 0.5 ** len(failures) that is a 4x difference in penalty between two single rooms. The tiered comparator inherits it directly, since n_hard is dominated by these cascades -- the search's primary key was partly a measure of config style. The two paths disagreed about the same room. A PRESENT room is checked on all three qualities regardless of declaration: get_space_params fills width and proportion from defaults, deriving width from size when absent, so programme-house's t2 declares size: alone and still gets a real width target of 1.633 it can fail on. Missing, it emitted one placeholder where b1 emitted three. The cascade stands in for the checks that could not run, and it stood in for the wrong number of them. Fix: emit all three placeholders always -- a fixed 5 per missing instance, mirroring the present-room path. 36 of 67 corpus codes were under-counted. Max weight ratio between two single rooms 4x -> 1x (programme-house), 2x -> 1x (harbor, maple). This makes fail counts LARGER and that is the point; it is a correctness fix, not an improvement. harbor evolved-3M-nols-3 82 -> 84, generated 155 -> 174, evolved-3M 131 -> 144; maple generated unchanged (no missing instances). NOT taken: 1i8's other option, one fail per instance with the placeholders informational. It fixes the verbosity dependence too but silently rescales a missing room from 1/32 to 1/2, the same weight as one crinkliness fail. Whether it SHOULD cost 1/32 is a real and separate question; bundling it here would change the objective's priorities under cover of a bug fix. Magnitude left exactly where it was, filed as homemaker-py-3i3. Every historical corpus fail count is invalidated again, on top of 39.4 and 38.10/38.11 -- which is why the cold-start re-baseline belongs after the objective work, not before it. Closes homemaker-py-1i8. Lint at parity (46); tests 379 passed (3 new), 0 failed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB |
||
|---|---|---|
| .. | ||
| 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 ⚡