Composition
How one template version's dependency tree runs on the user's machine as one unit, and how its outputs and answers are combined.
Composition owns one template version's dependency tree at run time: its run order, the answers that pass from node to node, the node cache, and laying the nodes' outputs into one file set.
It does not own:
- what a template, template group or conflict resolver is (authoring);
- pinning dependencies at push (registry);
- running one node's containers, or processor output merge (coordinator);
- asking one node's questions, headless envelopes (prompting);
- stacked templates, the three-way merge and the state file (project lifecycle).
Docs, in reading order
- Dependency tree - a template version plus every version it pins; nodes, groups, two versions of one template.
- Preset answer - a parent answers a dependency's question; types, first-wins merge, where the value goes.
- Composition run - the whole flow for one tree: flatten, each node, need input, layering.
- Dependency flattening - the run order: post-order, version id order, shared nodes, cycles.
- Answer namespacing - scoped and global answer keys when a tree has several nodes with images.
- Answer carry-over - the composition state from node to node; type clashes; pruning undone.
- Node cache - key, eligibility, file format, and where it serves the wrong answers.
- Dependency layering - per-path resolver votes, agreement, last layer wins, the group shift bug.
- Session release - the nested owners that release every coordinator session.
Across contexts: Conflict resolvers compares the two places conflict resolvers run.