gastownhall /

Beads

Live map
View repository
Snapshotmain · 7505e17

How bd turns an agent command into dependency-aware work stored in Dolt and synchronized between collaborators.

Click a building or route
Choose a path

Follow a new issue into durable storage and back out through the dependency-aware ready query.

System map8 components · 9 connections
130%
Beads: agent work as a versioned graph architectureStart at the CLI gate, follow a create or claim through the backend contract, then compare embedded storage with remote synchronization.argv, environment, opt…parsed flags and repos…issue fields, claim op…issue IDs, edge type, …unblocked issue recordsSQL rows for issues, d…Coding agentbd CLI gateWork commandsBackendcontractDependencygraphEmbedded DoltServermode APIDolt remote
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal

Terms, in plain English

BeadA durable issue record representing a task, bug, feature, message, or memory.

How to study this repo

  1. 1
    Trace one command

    Read cmd/bd/main.go and cmd/bd/create.go, then list every validation before storage is touched.

  2. 2
    Study dependency semantics

    Compare create_deps.go with ready.go to see how stored edges change executable work.

  3. 3
    Compare storage modes

    Read the embedded store and HTTP server paths; explain why single-writer and multi-writer deployments differ.