MuNa/.beads
Bruno Postle ac056ae21e Revise paper draft: fix narrative provenance, hedge unverified claims
Author fact-checks on paper/paper.md:
- Site area simplified to ~13,000 m2 throughout (drop pseudo-precise
  13,004.65 m2, even though it's genuinely in the official brief).
- Corrected a significant factual error: the two tracks are not fully
  independent - Track A's visitor narrative and half of Track B's merge
  input both descend from Salingaros' shared root narrative. Section 4
  rewritten around "divergent elaborations of a shared root", with the
  convergence claim re-evidenced from the material that actually is
  independent (3 of 4 Track A narratives, Track B's second merge input,
  both image-generation stages).
- Attributed Salingaros' image critique-loop account as self-reported,
  not independently verified, with image-numbering gaps noted only as
  circumstantial support.
- Added the authors' working hypothesis for the image-register gap:
  partly a deliberate medium request (watercolour vs unconstrained),
  partly that Track B's prompts carried the full pattern+form-language
  text inline per image vs Track A's short distilled per-scene prompts -
  clearly hedged as unverified.
- Fixed an overclaim that symposium participants judged both image sets;
  they only saw Track B's.
- De-emphasized the plan-layout idea throughout (title, abstract, intro,
  section 7, conclusion) to read as one possible future direction in
  prose, not work in progress.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-24 22:46:04 +01:00
..
hooks bd init: initialize beads issue tracking 2026-07-18 19:14:54 +01:00
.gitignore bd init: initialize beads issue tracking 2026-07-18 19:14:54 +01:00
config.yaml bd init: initialize beads issue tracking 2026-07-18 19:14:54 +01:00
interactions.jsonl Add generalized form-language prompt template 2026-07-24 19:53:36 +01:00
issues.jsonl Revise paper draft: fix narrative provenance, hedge unverified claims 2026-07-24 22:46:04 +01:00
metadata.json bd init: initialize beads issue tracking 2026-07-18 19:14:54 +01:00
README.md bd init: initialize beads issue tracking 2026-07-18 19:14:54 +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