implementation/
A map of this folder, made from each doc's meta block.
Docs here
- Answer carry-overalgorithmHow the composition state passes answers from node to node in one tree, fails on a type change, and undoes the headless pruning of unused answers.
- Answer namespacingalgorithmWhen a tree has more than one node with images, question ids can be scoped by version id - how keys are classified, stripped, and kept global or scoped.
- Dependency flatteningalgorithmHow one template version's dependency tree becomes one run order - post-order, siblings by version id, shared nodes once with merged presets, root last.
- Dependency layeringalgorithmHow the outputs of every node in one dependency tree are laid into one file set - per-path resolver votes, unanimous agreement, last layer wins, clash records.
- Node cachealgorithmThe on-by-default local cache of one node's output and answers - its key, who may use it, the file format, and the cases where it serves the wrong thing.
- Session releaseguardThe nested owners that make sure every coordinator session a create or update opens is released, on success, need input and failure.