composition map
Composition: map
Running one template version with its whole dependency tree and laying the outputs into one file set.
domain/
feature
- Dependency tree - A template version plus every template version it depends on, each fixed by version id at push.
- Preset answer - An answer a parent template version sets for a question of one of its dependencies.
architecture/
flow
- Composition run - How the composition operator runs one template version's tree: flatten, run each node or serve it from cache, then layer.
implementation/
algorithm
- Answer namespacing - How answers are scoped per template when a composition has more than one template with an image.
- Dependency flattening - How one template version's dependency tree becomes one ordered list of template versions to run, and why the order is what it is.
- Dependency layering - How the file outputs of every template version in one dependency tree are laid on top of each other, and how a file clash is settled.
- Node cache - A local cache of one node's file output so an unchanged node is not run again; on by default.
- Session release on failure - How coordinator sessions opened during a run are always released, even when a later step fails.