homemaker-layout/.beads
Claude 8a1b547285
bd: save session memories and re-scope bk9 for the post-39.25 objective
Memories stored via bd remember (injected at bd prime, so they survive into the
re-baseline session):

  config-declares-over-defaults      a CONF_DEFAULTS value is not the live one;
                                     the corpus configs declare their own
  absence-of-fails-means-nothing     zero fails can mean the check is disabled
  crinkliness-is-alexander-159       1/crink is depth PER WINDOW WALL
  score-is-already-a-ratio           value/cost makes per-m2 pricing
                                     proportional already
  fails-are-emitted-before-aggregation  why aggregation and rate changes cannot
                                     move the fail set
  objective-state-after-39.25        every default now live, and what is still
                                     default-OFF
  ab-protocol-and-mdd                the harness, and what 8000 evals can and
                                     cannot resolve
  none-of-39s-changes-are-search-proven

bk9 re-scoped: it was filed after 39.19 and four more changes have landed since
(39.22-39.25). Its comment now lists all six, names the two still default-OFF,
gives the rescored baseline layouts, and asks for four things beyond 39.12's
mean/sd/MDD -- per-storey daylit-wall supply/demand, the outdoor fraction (the
one unmeasured risk in 39.25), open space by storey, and corridor geometry.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB
2026-09-06 15:48:18 +00:00
..
hooks bd init: initialize beads issue tracking 2026-06-11 23:27:11 +01:00
.gitignore Ignore beads auto-import tracking marker 2026-08-25 23:01:40 +00:00
config.yaml Rename package: homemaker → homemaker-layout 2026-06-14 08:18:06 +01:00
issues.jsonl bd: save session memories and re-scope bk9 for the post-39.25 objective 2026-09-06 15:48:18 +00:00
metadata.json bd init: initialize beads issue tracking 2026-06-11 23:27:11 +01:00
README.md bd init: initialize beads issue tracking 2026-06-11 23:27:11 +01:00

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


Beads: Issue tracking that moves at the speed of thought