ralphy. Every generation, render, and log line is keyed by a project ID. This page walks the verbs that create, inspect, and mutate projects, plus the append-only log surface that backs every project’s memory. Per-verb flag detail lives in the auto-generated reference.
Two creation paths
ralphy new is the agent-facing entry-point: it creates a project under ~/.ralphy/projects/<id>/ (CWD-independent), seeds BRIEF.md from the argument, and touches the three append-only logs.
ralphy project create is the structured form for when you have a brand, persona, and template already picked. It writes to workspace/projects/<id>/ inside the active project root and registers the entity in workspace/.ralph/registry.json.
ralphy new when starting from a brief; use ralphy project create when scripting a batch from a template.
ralphy clone <url-or-ref>
clone is a meta-verb. Given a public URL (TikTok / Reels / Shorts / X) or an existing ref slug, it chains four back-stage verbs — ref pull → ref frames → ref analyze → ref blueprint — then writes a new vibe-style template under workspace/templates/clone-<slug>/.
--strict-look mirrors palette and grading in the blueprint; --prompt-only skips music and voice extraction; --as-template overrides the derived id. Full surface: /reference/cli/clone.
ralphy project list
Lists every registered project with derived status —done, assets, render, prompts, scenario, or draft. Status is recomputed from the filesystem on every call, so a stale registry never lies.
{ id, name, status, brand, persona, platform }.
ralphy project show <id>
Inspect a single project. By default it prints the canonical metadata; flags drill into sub-resources.--tree returns { project, root, fileCount, totalBytes, tree: [{ path, bytes }] } — useful for confirming what landed on disk before a render.
ralphy project update / delete
delete is registry-aware: it removes the entry from registry.json and the on-disk dir together. Per AGENTS.md invariant #13, this is the only blessed cleanup path. Don’t rm -rf workspace/projects/<id> by hand — you’ll desync the registry.
ralphy project log + timeline
Every project keeps three append-only JSONL files underlogs/. The verbs that read and write them:
ralphy project score / transcribe / verify / clone
Three utility verbs that don’t fit the CRUD shape:score raises E_GATE_SCENARIO when the scenario fails; see Error catalog. verify is the cheap pre-render check that catches missing slots, codec mismatches, and aspect drift.
Project ID conventions
The canonical shape is{context}-{NNN} (e.g. spring-2026-001). ralphy new falls back to YYMMDD-HHMMSS when no brief is supplied. Slot IDs inside a project follow {scene-id}-{type}-{descriptor} (e.g. scene-01-bg-image) — see Generation verbs.
Related
- Concepts: projects — the workspace layout
- Concepts: generation log — the JSONL shapes
- Resource CRUD — the unified verb shape that
projectfollows - cli/commands/project.ts, cli/commands/new.ts, cli/commands/clone.ts