Doc system test

composition map

Composition: map

domain/

  • Dependency tree - A template version plus every template version it pins, transitively, each a node by version id; groups are nodes that make no files.
  • Preset answer - A parent template version answers a dependency's question in cyan.yaml; only strings, booleans and string lists count, and the first value merged wins.

architecture/

  • Composition run - How one template version's whole dependency tree runs - flatten, then per node namespacing, presets, cache, live run and answer carry-over, then layering.

implementation/

  • Answer carry-over - How 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 namespacing - When 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 flattening - How 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 layering - How 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 cache - The 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 release - The nested owners that make sure every coordinator session a create or update opens is released, on success, need input and failure.