Create, end to end
What happens across the CLI, registry, coordinator and template containers from cyanprint create to files on disk.
cyanprint create atomi/web ./shop touches every context. This page is the map: each step names the context that owns it and links its doc.
Read it first, then go down into the step you care about.
The steps
sequenceDiagram
participant CLI
participant Registry
participant Coord as Coordinator
participant T as Template container
CLI->>Registry: get atomi/web (latest version)
CLI->>CLI: read .cyan_state.yaml, make specs
loop every spec, base then incoming
CLI->>Registry: fetch each dependency by version id
loop every node in run order
CLI->>Coord: template warm + session warm
CLI->>Coord: bootstrap session
loop until final reply
CLI->>Coord: proxy init (answers, deterministic state)
Coord->>T: init
T-->>CLI: question or Cyan
end
CLI->>Coord: build phase (Cyan)
Coord-->>CLI: tar.gz of files
end
CLI->>CLI: dependency layering
end
CLI->>CLI: stack, three-way merge, write, save state, run commands
CLI->>Coord: clean sessions| # | Step | Owner | Doc |
|---|---|---|---|
| 1 | Find the template version; references were pinned at push | registry | reference pinning |
| 2 | Read the state file; decide add, upgrade or rerun; make previous and current specs | project lifecycle | create, template stacking |
| 3 | Flatten each spec's dependency tree into a run order | composition | dependency flattening |
| 4 | For each node: warm-up and bootstrap | coordinator | template run, warm-up |
| 5 | Ask the questions through the proxy | prompting, coordinator | stateless replay, proxy routing |
| 6 | Build phase: processors, processor output merge, plugins, tar.gz | coordinator | build phase |
| 7 | Lay the nodes' outputs into one file set | composition | dependency layering |
| 8 | Stack the specs | project lifecycle | template stacking |
| 9 | Three-way merge with the folder; delete dropped files; write | project lifecycle | three-way merge |
| 10 | Save state; run post-template commands; clean sessions | project lifecycle, composition | state file, post-template commands, session release |
Where a conflict resolver can run
Twice per template version tree: in step 6 between processors, and in step 7 (and step 8) between template versions. The rules differ; see conflict resolvers.
Why so many runs
A folder with two stacked templates of three nodes each makes 12 template runs on one update: 2 specs × 3 nodes × (base + incoming). The node cache serves repeats. Inferred: this is the price of never storing the base.