Project lifecycle
The user's folder - the templates stacked in it, its state file, and how create and update change it. All project state lives here.
What this context owns. Everything that happens to a target folder: which templates are stacked in it, the state file that records them, and the batch run behind cyanprint create and cyanprint update that rebuilds the last run, makes the new one, and merges both with the user's edits.
What it does not own. How one template version and its dependencies are run and layered (composition), how questions are asked (prompting), containers and sessions (coordinator), versions and pinning (registry), and what a template is (authoring).
Start here: client-side state and determinism, the design every doc below hangs off, and the shop example, the one project every doc uses.
Docs, in reading order
| Doc | Type | One line |
|---|---|---|
| State file | format | the only record of a project: records, history, managed files, clashes |
| Create | feature | one command, three modes: new template, upgrade, rerun |
| Update | feature | every stacked template to a newer version, saved answers reused |
| Managed files | format (stub) | the paths the templates make, per template and as a union |
| File clash record | format (stub) | one file_conflicts entry |
| Template stacking | flow | many templates in one folder, replayed and laid oldest first |
| Batch run | flow | run twice, stack, merge once, write, save, run commands |
| Three-way merge | algorithm | merge base (rebuilt), local set, incoming set, one git merge |
| Post-template commands | algorithm | shell commands after the write, interactive and headless |
| Created folder cleanup | guard | a stopped headless run leaves the disk as it was |
| Output paths | guard | kept off this public page (security-related) |
| Git dirty check | guard (stub) | update stops or asks on uncommitted changes |