From 1706551df9794d3a9c9c78cf6e5003ea4516663d Mon Sep 17 00:00:00 2001 From: delchev Date: Wed, 19 Aug 2026 12:28:09 +0300 Subject: [PATCH] docs(glue): an expansion's rows do not outlive their master expansions describes the generated child set as owned by the expansion, but the page only said what a span CHANGE does. Deleting the master left the rows as the one part of the record that survives it - orphans still counted by every roll-up and report - and the page gave a reader no way to know that. --- docs/spec/glue.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/spec/glue.md b/docs/spec/glue.md index a2290ec..5e04738 100644 --- a/docs/spec/glue.md +++ b/docs/spec/glue.md @@ -503,6 +503,18 @@ expansions: A span change replaces the generated child set — never mix hand-entered rows into an expanded child. +::: info Normative +Deleting the master removes the rows the expansion generated for it. Only rows selected by the +expansion's own back-reference are removed, and each is removed through the child's layer, so the +child's delete event fires for every row and anything reacting to a deleted child reacts exactly as +it would for a hand-deleted one. The removal is idempotent. +::: + +The generated rows are the expansion's, not the author's, and that is what settles the question: +without this rule they would be the one part of a deleted record that survives it — still pointing at +an id that no longer resolves, still counted by every roll-up, report and balance that counted them +while the record existed. + ## generates — create-from One-click "create a document from this document":