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 3166d0a8f174557b68d1061a649d5ffda1aee4d5 Author: Stephen Mallette <[email protected]> AuthorDate: Mon Aug 10 09:01:45 2026 -0400 Pin code references in beads to a commit Cite code as file[sha] so a reference still resolves after the lines around it move. Line numbers and symbol names both drift. Assisted-by: Claude Code:claude-opus-5 --- .beads/PRIME.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.beads/PRIME.md b/.beads/PRIME.md index 6c69ddf421..9b87241a65 100644 --- a/.beads/PRIME.md +++ b/.beads/PRIME.md @@ -76,6 +76,11 @@ PRIME.md describes"), never a judgment ("rejected as worse"). A mechanism can be later: when the problem it names no longer applies, the option is worth reconsidering. A judgment cannot, so the option stays dead by default. The chosen decision needs a reason too. +**Cite code as `file[sha]`** — `GryoPool.java[bece4a34c7]`, with enough path to be unambiguous +(`pom.xml` is 36 different files). No line numbers, no symbol names: both drift, and the +sentence around the citation already says what it points at. The sha has to be reachable from a +published branch, because a local commit can be rebased away before it merges. + **Record what actually happened.** If you cannot point to the moment, do not write the bead. When you sense a decision you were not party to, create a bead labelled `human` posing the question instead of inventing an answer — `bd human respond <id>` turns the reply into a
