The code has 79 concepts, and the old docs explained only 16 of them correctly
16 covered, 5 partly, 28 wrongly and 30 never.
A concept is one idea that a reader must understand on its own
The last three pages covered the big mechanisms. But a reader meets many smaller ideas too. What is a Cyan? What does cyanprint try do? What does the tool exit with when it fails?
We call each of these a concept. A concept is one idea that needs its own explanation. Each one gets its own doc. It can be a thing, such as the state file. It can be a step, such as dependency flattening. It can also be a command, a file format or a rule.
This page lists all of them, not just the famous ones.
We read the code, then swept every named item into 79 concepts
The map comes from the code, not from the old docs. The core of the command-line tool was read by hand. Three helpers then swept the rest: the old docs, the server side, and every other command-line item.
The helpers found 194 named items Measured. Each one went into one of 79 concept docs. A small item, such as one flag, sits inside the doc of the concept it belongs to.
A later, wider sweep of the servers listed 1,431 rows Measured. It counted every config key, Helm value and error type. 620 of those rows belong to CyanPrint v4. The rest fall under the registry and coordinator docs.
Then each concept was checked against silicon. Nothing was run: each mark comes from reading the old page next to the code. There are four marks:
- CoveredSilicon explains it, and the explanation matches the code.
- PartlySilicon has it, but leaves out a part a reader needs.
- Covered wronglySilicon explains it, but says something the code does not do.
- Never coveredNo silicon page explains it at all.
"Covered wrongly" is the worst mark. A missing page sends a reader to the code. A wrong page sends them off with a false picture.
The old docs explained 16 of the 79 concepts correctly
Here is how all 79 concepts scored against silicon:
More concepts are explained wrongly than correctly: 28 against 16. A reader who trusts silicon gets the wrong picture more often than the right one.
The old docs did best where authors work, and worst in the machinery
The marks are not spread evenly. Group the concepts by bounded context, and a pattern shows.
Here is each context, split by mark. Compare authoring at the bottom with composition near the top:
- covered
- covered wrongly
- never covered
- partly
Show as table
| covered | covered wrongly | never covered | partly | Total | |
|---|---|---|---|---|---|
| Across contexts | 0 | 2 | 0 | 0 | 2 |
| Project lifecycle | 1 | 4 | 7 | 1 | 13 |
| Composition | 0 | 3 | 5 | 0 | 8 |
| Prompting | 3 | 2 | 4 | 0 | 9 |
| Coordinator | 2 | 4 | 6 | 2 | 14 |
| Registry | 3 | 3 | 6 | 0 | 12 |
| Authoring | 7 | 10 | 2 | 2 | 21 |
Concept map of the trial docs tree, read from the code, 18 Nov 2026.
Authoring has the most right: 7 of its 21 concepts Measured. Composition has none right: 3 wrong and 5 never mentioned. Project lifecycle, which owns your folder, gets 1 of 13 right.
Those two weak contexts hold the ideas from earlier pages: stacking, the merge, flattening and layering. They decide which files land in your folder. Every one of the eight concepts we wrote in full was covered wrongly Measured.
Now look at the 16 that silicon got right. Most are things a user names: a template, a question, an answer, an artifact, the create command. So silicon named the parts well, but went wrong on how they work together Estimate.
You can browse all 79 concepts and filter them by context and mark
Each card below is one concept, with its one line and its old-docs mark. A card opens that concept's doc in the new docs tree. The eight marked "full doc" carry a long worked example.
Use the chips to narrow the list. Try Composition, or "never covered":
Context
Old docs
Showing 79 of 79 concepts
Across contexts 2 concepts
- Conflict resolversfull doc covered wronglyWhere a conflict resolver runs, the two different rules that pick one, and the request it gets.architecture/conflict-resolvers.md
- Create, end to endfull doc covered wronglyWhat happens across the CLI, registry, coordinator and template containers from cyanprint create to files on disk.architecture/create-flow.md
Project lifecycle 13 concepts
- Batch run never coveredThe shared run behind create and update: run previous and current specs, stack each list, three-way merge, write, save state, run commands.domain/project-lifecycle/architecture/batch-run.md
- Template stackingfull doc covered wronglyHow several templates installed into one target folder are run side by side and laid on top of each other on the user's machine.domain/project-lifecycle/architecture/template-stacking.md
- Create coveredcyanprint create: add a template to a target folder, or rerun or upgrade it if the folder already has it.domain/project-lifecycle/domain/create.md
- File clash record never coveredThe file_conflicts list in the state file: every file clash of the last run and how it was settled.domain/project-lifecycle/domain/file-clash-record.md
- Managed files never coveredThe list of paths the stacked templates make, kept in the state file per template and as one union.domain/project-lifecycle/domain/managed-files.md
- State file covered wronglyThe .cyan_state.yaml file in a target folder: one record per stacked template, plus managed files and file clash records.domain/project-lifecycle/domain/state-file.md
- Update covered wronglycyanprint update: move every stacked template in a target folder to its latest version, or a picked one.domain/project-lifecycle/domain/update.md
- Created folder cleanup never coveredHow a headless create that stops on a question removes the folders it made, leaving the disk as it was.domain/project-lifecycle/implementation/created-folder-cleanup.md
- Exit codes and errors never coveredWhat the CLI exits with on success and failure, interactive and headless.domain/project-lifecycle/implementation/exit-codes.md
- Git dirty check partlyWhy update stops on uncommitted changes, and what it does without git or in headless mode.domain/project-lifecycle/implementation/git-dirty-check.md
- Output paths never coveredHow paths from template output and resolver replies become files on disk.domain/project-lifecycle/implementation/output-path-safety.md
- Post-template commands never coveredHow the commands that templates list are run in the target folder after files are written.domain/project-lifecycle/implementation/post-template-commands.md
- Three-way mergefull doc covered wronglyHow create and update fold new template output into a target folder without losing the user's edits, and why the base is rebuilt instead of stored.domain/project-lifecycle/implementation/three-way-merge.md
Composition 8 concepts
- Composition run never coveredHow the composition operator runs one template version's tree: flatten, run each node or serve it from cache, then layer.domain/composition/architecture/composition-run.md
- Dependency tree covered wronglyA template version plus every template version it depends on, each fixed by version id at push.domain/composition/domain/dependency-tree.md
- Preset answer never coveredAn answer a parent template version sets for a question of one of its dependencies.domain/composition/domain/preset-answer.md
- Answer namespacing never coveredHow answers are scoped per template when a composition has more than one template with an image.domain/composition/implementation/answer-namespacing.md
- Dependency flatteningfull doc covered wronglyHow one template version's dependency tree becomes one ordered list of template versions to run, and why the order is what it is.domain/composition/implementation/dependency-flattening.md
- Dependency layeringfull doc covered wronglyHow 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.domain/composition/implementation/dependency-layering.md
- Node cache never coveredA local cache of one node's file output so an unchanged node is not run again; on by default.domain/composition/implementation/node-cache.md
- Session release on failure never coveredHow coordinator sessions opened during a run are always released, even when a later step fails.domain/composition/implementation/session-release.md
Prompting 9 concepts
- Headless envelope never coveredThe one JSON object a headless run prints on stdout: done, need_input with the question, or error.domain/prompting/architecture/headless-envelope.md
- Headless mode never coveredRunning create, update or try without a terminal: answers come from a file or stdin, and one JSON envelope goes to stdout.domain/prompting/architecture/headless-mode.md
- Answer coveredA value for one question: a string, a list of strings, or a boolean, stored as { type, value }.domain/prompting/domain/answer.md
- Deterministic state covered wronglyValues a template makes once with d.get, such as a UUID or date, kept the same across the replays of one run.domain/prompting/domain/deterministic-state.md
- Prompt outcome never coveredThe end state of one prompt run: complete with answers and Cyan, need input, or error.domain/prompting/domain/prompt-outcome.md
- Question coveredOne prompt a template asks: text, password, select, checkbox, confirm or date, with an id, message and optional validator.domain/prompting/domain/question.md
- Answer validation coveredHow a typed or supplied answer is checked by the template's own validator before it is accepted.domain/prompting/implementation/answer-validation.md
- Secret redaction never coveredHow headless errors are kept from echoing a supplied answer, so a password never reaches the JSON envelope.domain/prompting/implementation/secret-redaction.md
- Stateless replayfull doc covered wronglyHow the CLI asks a template's questions one at a time by re-running the template script from the top with every answer so far.domain/prompting/implementation/stateless-replay.md
Coordinator 14 concepts
- Coordinator API partlyEvery HTTP route the coordinator serves on port 9000, one line each.domain/coordinator/architecture/api-surface.md
- Coordinator hosting never coveredWhere the shared coordinator runs: OpenTofu code for a host on AWS, DigitalOcean or Vultr, and DNS for coord.cyanprint.dev.domain/coordinator/architecture/hosting.md
- Proxy routing never coveredHow a CLI call reaches a shared template or resolver container by version id, through the coordinator.domain/coordinator/architecture/proxy-routing.md
- Template run on the coordinator covered wronglyThe calls one template run makes: template warm and session warm, bootstrap, the question loop through the proxy, then the build phase.domain/coordinator/architecture/template-run.md
- Blob volume covered wronglyA shared, read-only Docker volume holding a template version's files, filled once from its blob image.domain/coordinator/domain/blob-volume.md
- Container naming never coveredHow a container or volume name is built from kind, version id and session, and why names are the routing table.domain/coordinator/domain/container-naming.md
- Daemon coveredThe coordinator run on the user's own machine as a Docker container, started and stopped by cyanprint daemon.domain/coordinator/domain/daemon.md
- Session never coveredA run-scoped id that owns one template run's processor, plugin and merger containers and its work volume.domain/coordinator/domain/session.md
- Build phase covered wronglyWhat POST /executor/{session} does: run processors, merge their outputs, run plugins, return a tar.gz of the files.domain/coordinator/implementation/build-phase.md
- Cleanup coveredHow one session, or the whole pool, of coordinator containers, volumes and images is removed.domain/coordinator/implementation/cleanup.md
- Processor output mergefull doc covered wronglyHow the merger container joins the output folders of one template's processors, and settles a path two processors both wrote.domain/coordinator/implementation/processor-output-merge.md
- Readiness checks never coveredHow the coordinator waits for containers to answer, and the case where it reports ready without an answer.domain/coordinator/implementation/readiness-checks.md
- Try setup never coveredHow the coordinator prepares a local, unpublished template for cyanprint try: a blob volume from an image or a folder under DEV_ROOT.domain/coordinator/implementation/try-setup.md
- Warm-up partlyHow the coordinator makes a template version ready: pull images, fill the blob volume once, start shared template and resolver containers, health-check.domain/coordinator/implementation/warm-up.md
Registry 12 concepts
- Registry config options never coveredThe registry's settings: named option groups (database, cache, storage, auth and more), each with defaults, checked at start.domain/registry/architecture/config-options.md
- Registry deployment never coveredHow the registry runs: a Helm chart for the API, a separate Helm chart for the migration job, both set by LANDSCAPE.domain/registry/architecture/deployment.md
- Registry errors never coveredThe typed problems the registry returns, as problem-details JSON: validation error, entity not found, unauthorized and others.domain/registry/architecture/error-contract.md
- Registry UI covered wronglyThe web catalog (argon): browse and search the four artifact kinds, see versions and links, manage API tokens.domain/registry/architecture/registry-ui.md
- Artifact version coveredOne numbered release of an artifact: its own GUID (the version id), an integer version number, images and links.domain/registry/domain/artifact-version.md
- Artifact coveredOne of the four kinds of thing the registry holds: template, processor, plugin, conflict resolver; each owned by a user.domain/registry/domain/artifact.md
- Push covered wronglycyanprint push: publish a new version of a template, template group, processor, plugin or resolver from cyan.yaml.domain/registry/domain/push.md
- Search and stats covered wronglyHow artifacts are searched, and what stars, downloads and dependency counts mean.domain/registry/domain/search-and-stats.md
- User and API token coveredA registry account (external id plus username) and the named, revocable API tokens the CLI pushes with.domain/registry/domain/user-and-token.md
- Registry migrations never coveredHow the migration job prepares the database and the file bucket before the registry serves.domain/registry/implementation/migrations.md
- Reference pinning never coveredHow push turns username/name[:version] references into fixed version ids, with a missing or 0 version meaning the latest at push time.domain/registry/implementation/reference-pinning.md
- Run-time name lookup never coveredHow the coordinator turns a processor or plugin name in a Cyan into a version id, staying inside the template's declared versions.domain/registry/implementation/runtime-name-lookup.md
Authoring 21 concepts
- SDK servers covered wronglyHow each SDK (Node, Python, .NET) wraps an author's function in an HTTP server, one fixed port per artifact kind.domain/authoring/architecture/sdk-servers.md
- Artifact reference covered wronglyHow cyan.yaml and the CLI write a reference to another artifact: username/name or username/name:version.domain/authoring/domain/artifact-reference.md
- Artifact test coveredcyanprint test: run a template, processor, plugin or resolver against saved inputs and compare its output with saved snapshots.domain/authoring/domain/artifact-test.md
- Conflict resolver coveredAn artifact that merges several versions of one file into one, such as two package.json files.domain/authoring/domain/conflict-resolver.md
- Cyan glob coveredA file selection in a Cyan: root, glob, excludes, and a mode - template (hand files to the processor) or copy (copy bytes as they are).domain/authoring/domain/cyan-glob.md
- cyan.yaml partlyThe artifact's config file: identity and metadata, and for a template its processors, plugins, templates (with preset answers), resolvers and commands.domain/authoring/domain/cyan-yaml.md
- Cyan covered wronglyA template's final answer: the list of processors (with globs and config) and plugins (with config) to run.domain/authoring/domain/cyan.md
- Determinism helper covered wronglyThe SDK's d.get(key, make): the way a template makes a random or time value that stays the same across replays.domain/authoring/domain/determinism-helper.md
- Dev config coveredThe dev section of cyan.yaml: try a template whose script runs on your machine at a URL, with files from a local blob folder.domain/authoring/domain/dev-config.md
- Image build coveredcyanprint build: build an artifact's Docker images with buildx.domain/authoring/domain/image-build.md
- Inquirer coveredThe SDK object a template script asks questions with: text, password, select, checkbox, confirm, date.domain/authoring/domain/inquirer.md
- Plugin covered wronglyAn artifact that edits the merged output folder of a template after its processors ran.domain/authoring/domain/plugin.md
- Processor covered wronglyAn artifact that reads selected template files and writes transformed files into its own output folder.domain/authoring/domain/processor.md
- Template group partlyA template with no images: it only lists other templates (with preset answers) and resolvers, and makes no files itself.domain/authoring/domain/template-group.md
- Template coveredAn artifact that asks questions and returns a Cyan: which processors and plugins to run on its files.domain/authoring/domain/template.md
- Test config covered wronglyThe test.cyan.yaml file: the cases an artifact test runs - answers or inputs, expected output folder, optional commands.domain/authoring/domain/test-config.md
- Try covered wronglycyanprint try: run an unpublished local template, or template group, through a local coordinator before pushing.domain/authoring/domain/try.md
- Env substitution never coveredHow ${VAR} and ${VAR:-default} are filled in the build and dev sections of cyan.yaml.domain/authoring/implementation/env-substitution.md
- Snapshot comparison covered wronglyHow an artifact test compares actual output with the saved snapshot folder.domain/authoring/implementation/snapshot-comparison.md
- Test init covered wronglyHow cyanprint test init walks a template's question tree to write test cases and first snapshots.domain/authoring/implementation/test-init.md
- Try run never coveredHow cyanprint try runs a local template: a stand-in template version, a local template container, and output written without a merge.domain/authoring/implementation/try-run.md
"Never covered" is the largest group, with 30 concepts. Many of them are about failure: session release on failure, readiness checks, exit codes. A reader needs those exactly when something breaks.
CyanPrint v4, called sulfone.lite, is left out of this map on purpose
sulfone.lite is CyanPrint v4, release 4.10.2. It is a rewrite in TypeScript. Its artifacts run as local Bun code, not in Docker containers, and it has no coordinator.
It keeps the core ideas. Resolver votes stay, now in three tiers, and so does the three-way merge with a rebuilt base. It also fixes gaps in this map: for example, deterministic state is saved.
So it is a different product, with different words. It would need its own docs tree. That tree would keep five of these six contexts, and add trust and probes. We did not build it here.