Clarify immutable element sharing lifecycle

2026-11-10 16:14:09 +08:00
parent a6092e61cd
commit 69eb29343e
1 changed files with 5 additions and 3 deletions
@@ -858,9 +858,11 @@ same. Replacing a table gets a new entry view and leaves prior images unchanged.

 Static element validation proofs apply only to records detached and deeply frozen
 by the core's element-data factory. Document construction, element replacement
-and staged creations share this private provenance. A separate WeakSet records a
-successful intrinsic shape check. Registry support, tombstones, owner membership and connection topology remain
-live checks. Custom schemas are always called with their original receiver.
+and staged creations share this private provenance. Re-enveloping an already
+owned record preserves its immutable value identity instead of cloning it again;
+external and lookalike inputs are still detached. A separate WeakSet records a
+successful intrinsic shape check. Registry support, tombstones, owner membership
+and connection topology remain live checks. Custom schemas are always called with their original receiver.
 Only framework-owned data-only validators can reuse a successful result for the
 same detached record and current validator function; their private proof keeps
 one validator identity per record.