diff --git a/plans/composition-objects.md b/plans/composition-objects.md
index 726f7c3a..3d555d4e 100644
--- a/plans/composition-objects.md
+++ b/plans/composition-objects.md
@@ -57,6 +57,35 @@ responsive/personalised/variant space; rendering picks the path. Render-fold and
 behaviour interpreter are the **same shape** — interpreters over content-addressed objects + the
 decidable-core predicate set + the graph. The system converges on: objects + small interpreters.
 
+## Beyond content — composition is universal; a fold per domain
+
+The render-fold isn't "the content renderer" — it's **fold #1**. The composition DAG is a
+**universal algebra** (`seq/par/alt/each` over content-addressed objects); *content* is just one
+*interpretation*. Same structure, a different **fold** per domain — what changes is what the
+combinators and leaves *mean*:
+
+| domain | the fold | `seq` | `par` | `alt`+`when` | `each` | substrate |
+|--------|----------|-------|-------|-----------|--------|-----------|
+| **content** | render → HTML | block order | layout/columns | choose variant | map items | `compose.sx` (done) |
+| **behaviour** | execute → effects | steps in order | concurrent | branch (if/cond) | for-each | `[[project_flow_on_sx]]` |
+| **query** | eval → results | join/chain | union | conditional | iterate/quantify | `[[project_relations_on_sx]]` (Datalog) |
+| **pipeline** | reduce → data | dataflow stages | parallel ops | choose path | fan-out | `[[project_artdag_on_sx]]` (content-addressed DAG) |
+| **types** | extent → set | — | ∧ intersection | — | ∨ union | the type algebra (`make-and!`/`make-or!`) |
+
+So **"relations just a fork" generalises**: a `contains` fork folded by *render* is a document; a
+`then` fork folded by *execute* is a workflow step; a `depends-on` fork folded by *eval* is a
+dependency graph. **The relation kind + the fold = the domain.** This isn't aspirational — the
+repo's `X-on-sx` loops ALREADY ARE these folds (flow = execute, Datalog = eval, artdag = a
+content-addressed composition DAG); we just hadn't seen them as one shape. The composition DAG is
+the **convergence point** the whole fleet has been circling.
+
+The payoff is concrete: **build the composition machinery ONCE** (forks + ordered edges + the four
+combinators + a fold framework) → reuse for every domain by writing one interpreter. **The block
+editor edits *any* composition** — author a workflow like a document, same structure, one editor.
+The whole system collapses to four ideas: **content-addressed objects + a composition algebra +
+per-domain folds + the decidable-core predicates (`when`).** The render-fold's shape (walk the
+composition, dispatch combinators, recurse, read the context) is the *template* for every other fold.
+
 ## What lives elsewhere (not composition primitives)
 
 Transclusion = a `ref` leaf. Sort/filter/limit/group = the *source query* language (Datalog).
@@ -76,3 +105,13 @@ Transclusion = a `ref` leaf. Sort/filter/limit/group = the *source query* langua
 5. The typed importer decomposes Ghost Lexical into card objects + a `contains` body (cards-as-
    objects), instead of one `sx_content` string.
 6. The block editor edits the body (insert/reorder/`alt`/`each`) — the metamodel editor for content.
+7. **Prove universality with a second fold.** Write a tiny `execute`-fold over the *same*
+   `seq/alt/each` structure that *runs* a workflow (leaves = effects; `seq` = steps in order, `alt`
+   = branch, `each` = for-each) — the way the recursive tree proved recursion, this proves the
+   composition algebra is domain-agnostic. Then the *behaviour* model (Slice 9) is "an `execute`-fold
+   over a composition object", not a separate system.
+8. **Factor out the shared machinery** once two folds exist: the fork model (ordered, labelled,
+   `when`), the combinator dispatch, the context-environment, and recursion become a reusable
+   `compose` core; each domain (`render`, `execute`, `eval`, …) supplies only its leaf + combinator
+   semantics. The block editor + the metamodel UI then generalise to *every* fold — one composition
+   editor authors documents, workflows, queries, and pipelines alike.