(tinkerpop) 09/14: Correct where a new bead's labels are copied from

[sp...@apache.org]

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 7029f18eade8d81815fca223e7a07fe6d167419a
Author: Stephen Mallette <st...@amazon.com>
AuthorDate: Sun Aug 9 09:05:27 2026 -0400

    Correct where a new bead's labels are copied from
    
    A child copies its immediate parent's labels, not the root's, so a
    grandchild born under a stale child inherits the stale set. Measured
    on bd 1.1.2.
    
    Assisted-by: Claude Code:claude-opus-5
---
 .beads/PRIME.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/.beads/PRIME.md b/.beads/PRIME.md
index d2ceb72572..2c1ef27a94 100644
--- a/.beads/PRIME.md
+++ b/.beads/PRIME.md
@@ -244,10 +244,11 @@ bd label list-all                        # what is in use — includes drift; th
 ```
 
 **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.
+them, navigate to the root. Do not label children — `bd create --parent` copies the *parent's*
+labels onto a child at birth and never again. Siblings born either side of a relabel disagree,
+and at depth each level snapshots the level above, so the copies drift further the deeper they
+sit. 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