beads/ROADMAP.md
Julian Knutsen 0773e6334e
docs(agents): contributor-only agent instructions and documented-issue intake (#7223)
Makes the repo's agent and contributor surface describe developing beads, not using bd, and requires every PR to link a documented issue.

- Contributor-only root AGENTS.md with a routing table; cmd/bd/AGENTS.md and engdocs/AGENTS.md seam files; CLAUDE.md symlinks so Claude Code loads nested files.
- Bug and feature issue forms, a PR template that requires Closes #, CONTRIBUTING sections for the triage and pipeline labels, and the opt-in fork-cache during dev setup.
- ROADMAP.md for 1.4: versioned beads (#6132), Graph Preview 2 (#7170), contributor onboarding (#7228).
- docsync guards: root AGENTS.md at or under 20 KB; every AGENTS.md symlinked, routed, and with resolving links, paths, and guard-test names.

Agent-Signature: claude-code-claude-opus-5-5-high on behalf of Julian Knutsen
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-05 08:43:53 +00:00

3.3 KiB

Beads Roadmap

Last updated: 2026-10-05 · Owner: @julianknutsen

This page lists the areas the maintainers are prioritizing. It reflects current thinking, not commitments or dates: priorities change as we learn, and the live state of each item is its tracking issue on GitHub.

How this roadmap is used

  • Priority areas get expedited review. Issues and PRs that advance a priority area below are triaged and reviewed first.
  • Every PR links a documented issue. To propose work — inside or outside a priority area — open an issue with the feature form, before or alongside your PR; see CONTRIBUTING.md.
  • Scope. Proposals must fit the product boundary in engdocs/PROJECT_CHARTER.md.
  • Updates. The owner rewrites this page at each minor release; the date above says when it was last reviewed.

Priority areas for 1.4

Versioned beads and history

  • Goal: every change to a bead is recorded as a version. Users can read a bead's history and past versions, and writers can use expectedRevision compare-and-swap to avoid lost updates. Everything ships behind a flag, off by default, until the conformance suite and a production-corpus soak say otherwise.
  • This period: all six phases, enabled from the CLI by the end of the period: conformance suite (#6133), additive schema (#6134), dual-write history behind a flag (#6135), versioned reads and CAS (#6136), production-corpus validation (#6137), and CLI surfacing and enablement (#6138).
  • Tracking issue: #6132; design discussion stays on #5898.

Beads Graph Preview 2

  • Goal: ship Beads Graph Preview 2, the next public checkpoint for the generic Bead-and-Link graph model: a coherent daily-use CLI journey in graph mode that behaves like ordinary bd, backed by a complete, reviewable CLI specification.
  • This period: the reviewed graph CLI specification, a complete daily-use Issue journey proven through the installed CLI on embedded and shared-server Dolt, and editing around that Issue (labels, notes, Memory and Link edits).
  • Tracking issue: #7170

Contributor onboarding

  • Goal: a new contributor, human or agent, finds the rules for the code they are changing next to that code, understands its intent and invariants, and lands a change with a documented issue and PR.
  • This period: contributor-only agent instructions and documented-issue intake (#7223); per-package AGENTS.md files for the storage packages, naming their guard tests and lint rules; a package-doc linter and package docs for the packages that have none; and a curated set of help wanted starter issues.
  • Tracking issue: #7228