Bruno Postle
e95a3477a8
The constructive seeder was never nondeterministic: _assign_adjacency_aware ends every max/min with a unique leaf-idx tiebreak and uses set unions only for membership, so iteration order never leaks. constructive_topology(seed=0) is byte-identical across processes for every example programme. The cited "sig 4480 vs 16064" was a measurement artifact — Python's builtin hash() of a str is salted per process (PYTHONHASHSEED), so an identical signature hashes to different ints run-to-run. The real run-to-run noise was parallel-only: driver._run_batch admitted futures via as_completed (completion order), and admit() is order-sensitive (accrues n_evals per result; keeps the first individual of an equal-key tie as best). A long parallel run diverged 167 vs 161 fails (maple seed 0). Fix: admit futures in submission order (block on each result in turn; all still run concurrently), reproducing the serial admission sequence. Two workers=4 runs are now byte-identical. Serial (workers=1) was already byte-for-byte reproducible. Per-seed numbers are reproducible only at a fixed worker count; serial != parallel is expected (children/iteration 1 vs n_workers changes batch granularity). - driver: iterate futs in submission order, not as_completed - test: test_search_parallel_is_reproducible (fails on pre-fix, passes on fix) - DESIGN.md §12.4: corrected the reproducibility note Closes homemaker-py-xcy Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 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 ⚡