A guide is only as good
as its starting conditions.
Find missing prerequisites and incompatible versions.
Repair a fictional runbook without running a single command.
Published guide · Starter
Build a paper town
Assemble an imaginary town from a blueprint, then render a miniature preview. An older CLI meets a newer scene format.
- 01
Prepare the town scene
The scene builder needs an empty workspace and the paper-town blueprint.
grove toy init --blueprint paper-townFictional example · displayed only, never executed
Needs workspace, blueprintProduces town-scene- DependencyMissing workspace
This step needs toy workspace. Mark it available in the experiment to supply “workspace”.
- DependencyMissing blueprint
This step needs paper-town blueprint. Mark it available in the experiment to supply “blueprint”.
- VersionGrove CLI version conflict
Selected v1; this step supports v2–v3. Only published releases in that interval are compatible.
- DependencyMissing workspace
- 02
Render a miniature preview
The preview format is supported by Loom Engine v2 and v3.
loom toy preview --scene paper-townFictional example · displayed only, never executed
Needs town-sceneProduces town-preview- DependencyMissing town scene
“Prepare the town scene” could supply “town-scene”, but its own checks failed. Resolve that earlier step first.
- VersionLoom Engine version conflict
Selected v4; this step supports v2–v3. Only published releases in that interval are compatible.
- DependencyMissing town scene
- 03
Review the pretend skyline
Review the preview in this imaginary workflow. No files are created here.
grove toy review --preview paper-townFictional example · displayed only, never executed
Needs town-previewProduces town-reviewed- DependencyMissing town preview
“Render a miniature preview” could supply “town-preview”, but its own checks failed. Resolve that earlier step first.
- VersionGrove CLI version conflict
Selected v1; this step supports v2–v3. Only published releases in that interval are compatible.
- DependencyMissing town preview
Structured content. Explainable findings.
Sanity stores tool releases, capability prerequisites and ordered guide steps. This snapshot was queried at build time; deterministic browser checks explain each dependency and version conflict. Everything here is fictional. Content updates require rebuilding.