giles
1c2bf505f4
Some checks failed
Test, Build, and Deploy / test-build-deploy (push) Failing after 40s
The composition DAG is not a content mechanism; render is fold #1. The same structure (content-addressed objects + ordered labelled forks + seq/par/alt/each) is interpreted by a different fold per domain: content=render, behaviour=execute (flow-on-sx), query=eval (Datalog), pipeline=reduce (artdag, literally a content-addressed composition DAG), types=extent (and/or = intersection/union). "Relations just a fork" generalises: relation kind + fold = domain. The X-on-sx loops already ARE these folds — the composition DAG is the fleet convergence point. Payoff: build composition once, reuse per domain via interpreters; the block editor + metamodel UI generalise to every fold (author a workflow like a document). System collapses to four ideas: content-addressed objects + composition algebra + per-domain folds + decidable-core predicates. Roadmap +2: prove universality with a second (execute) fold over the same seq/alt/each; then factor out the shared compose core. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>