This is an automated email from the ASF dual-hosted git repository. spmallette pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit 22191a8ce33e263a3d4798a4ab50ef6e748bd32c Author: Stephen Mallette <[email protected]> AuthorDate: Mon Aug 10 10:15:05 2026 -0400 Attach the external artifact to the root bead Records the JIRA, PR, proposal or dev list thread on the root, since that is the only link from a bead back to the code. Optional for a small fix that never had one. Assisted-by: Claude Code:claude-opus-5 --- .beads/PRIME.md | 3 +++ docs/src/dev/developer/for-committers.asciidoc | 10 +++++++++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/.beads/PRIME.md b/.beads/PRIME.md index 9b87241a65..b71d5f043f 100644 --- a/.beads/PRIME.md +++ b/.beads/PRIME.md @@ -103,6 +103,9 @@ bd children <root> # recursive — the whole subtree notice a bead the work has since outgrown. - **If no root is selected, you are starting something new — create the root before writing code.** +- **Ask for the external artifact whenever you create a root** — JIRA, PR, proposal, dev@ + thread. Only the operator knows which one, and a record is the sole link from the work back + to the code (section 6). A small fix may genuinely have none, so take that answer and move on. - A small fix is a lone bead. It is its own root; don't hunt for a parent. - The operator may decline binding to a bead, in which case ignore these rules. diff --git a/docs/src/dev/developer/for-committers.asciidoc b/docs/src/dev/developer/for-committers.asciidoc index e4ed26ebaa..0525c1ecbd 100644 --- a/docs/src/dev/developer/for-committers.asciidoc +++ b/docs/src/dev/developer/for-committers.asciidoc @@ -126,7 +126,15 @@ later will think to search. An existing root is the right answer when the work continues something already under way, and a new root is the right answer when it does not. A small fix is often its own root (i.e. a single -bead) rather than a child of something larger. +bead) rather than a child of something larger. + +Most work is anchored by something outside the repository, such as a JIRA issue, a pull request, +a proposal, or a thread on the dev mailing list. That reference belongs on the root as a record +bead, and supplying it falls to the committer, because an agent has no way to know which ticket +or thread a piece of work belongs to. The link carries weight because records are the only +connection between a bead and the code, given that commit messages hold no bead identifiers. +It is not mandatory. A small fix that never had a ticket needs no record, and +`bin/beads-report.py` accordingly reports a root without one as a question rather than a defect. [[beads-decisions]] === What Beads Records
