From 69eb29343e718aa762c33e34171353eb51bc2d4b Mon Sep 17 00:00:00 2001 From: Codex Bot Date: Tue, 10 Nov 2026 16:14:09 +0800 Subject: [PATCH] Clarify immutable element sharing lifecycle --- headless/README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/headless/README.md b/headless/README.md index f9cc400..56e2a3b 100644 --- a/headless/README.md +++ b/headless/README.md @@ -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.