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 c080b852c619b9d62e6f92b0da5c6d0ddd4ccca5 Author: Stephen Mallette <[email protected]> AuthorDate: Mon Oct 12 13:17:47 2026 -0400 Require bead citations to use a release-branch sha Assisted-by: Claude Code:claude-opus-5-5 --- .beads/PRIME.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.beads/PRIME.md b/.beads/PRIME.md index 168cfa8347..fbc233ad57 100644 --- a/.beads/PRIME.md +++ b/.beads/PRIME.md @@ -89,8 +89,11 @@ rather than recalling, you are guessing. **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. +sentence around the citation already says what it points at. The sha has to be on a release +branch — `3.7-dev`, `3.8-dev` or `master`. A feature branch does not count, even once pushed: +squash and rebase rewrite it before it merges, and its shas stop existing, just as a local +commit's do. Code that exists only on the feature branch is cited by file alone — +`TinkerStorage.java` — and means the file as it is on that work's branch. **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
