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 45eb5a74a97d6df1ecd95a5b316561742009fb1f Author: Stephen Mallette <[email protected]> AuthorDate: Sun Aug 9 09:03:11 2026 -0400 Put dimension labels on the root bead only Children copy a root's labels at birth but never pick up one added later, so a label read off a child is unreliable. Read dimensions by navigating to the root instead. Structural labels are unaffected. Assisted-by: Claude Code:claude-opus-5 --- .beads/PRIME.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.beads/PRIME.md b/.beads/PRIME.md index bd0281721e..d2ceb72572 100644 --- a/.beads/PRIME.md +++ b/.beads/PRIME.md @@ -243,8 +243,11 @@ bd label list <id> bd label list-all # what is in use — includes drift; this file is the authority ``` -**Set module and release labels once on the root** — children inherit them. Labels added to -a root *after* its children exist do not backfill, so label the root first. +**Label the root, and only the root.** A bead's dimensions are its root's dimensions: to read +them, navigate to the root. Do not label children — `bd create --parent` copies the root's +labels onto a child at birth, but a label added later never reaches one, so per-child labels +are wrong as often as they are right. The structural labels below are the exception; they +describe the bead itself and belong wherever they apply. ### Structural labels — part of the data model, never optional
