024311a2c2
§39.9 named the upstream fix: keep circulation connected DURING the resize rather than rebuilding it after. Built and measured. It does not help, and the reason matters more than the lever. Both halves of the re-cut do damage, in different proportions per programme. Freezing rotations and letting only ratios move (% levels connected, 12 seeds): harbor 100 -> 71 -> 50, health-centre 100 -> 8 -> 8, maple 100 -> 92 -> 67. So health-centre is destroyed entirely by the ratio and maple mostly by the rotation; a fix must be able to give back either. operators._size_divisions_preserving_circulation snapshots every cut, resizes, then reverts the cuts on the tree path between each circulation pair the resize broke -- programme fully intact, no retyping, only geometry given back. It works on connectivity (harbor 50->92%, maple 67->97%, health-centre 8->17%) and costs area accuracy: constructed-seed fails harbor 96.6->141.5, maple 141.8->175.8, size fails roughly double. (A greedy single-cut revert barely moved -- it stalls where no ONE revert helps though two would. Targeting the broken pairs is what made connectivity work.) The obvious defence -- raw constructed seeds understate it, the resize is only a warm start, the inner loop should recover -- was TESTED AND FAILS. Full search, harbor-house, 12000 evals, seed 1: OFF 43 fails, 9 hard, 3 connectivity ON 65 fails, 26 hard, 4 connectivity Worse on every axis, including connectivity itself. REFRAMING: §39.9's fact stands (the resize destroys 41 of 49 circulation edges) but is NOT ACTIONABLE, because construction-time connectivity does not determine final connectivity. The search discards and rebuilds the seeder's circulation either way, and constraining the seed only spends area quality the search cannot recover. Together with §39.8 (not an incentive problem) that retires the framing this thread inherited from §38: connectivity is neither a construction problem nor an incentive one. Both flags (repair_circulation, preserve_circulation) stay default off with the numbers recorded, plus byte-identical-default tests. Do not revisit either without a new formulation -- the standing this document gives bubble.py. 356 passed (+1 new), same 7 pre-existing fixture failures, lint unchanged. 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 ⚡