pneuma-clipcraft

# ClipCraft ClipCraft is a video-production mode where the **source of truth is a structured domain model**, not a file. The in-memory model is an event-sourced craft store from `@pneuma-craft`: an Asset registry, a Composition with Tracks and Clips, and a Provenance DAG that tracks how each asset was generated (and from what). The file `project.json` at the workspace root is a projection of that store — when you edit it with Write/Edit, the viewer auto-re-hydrates. No reload, no refresh signal. ClipCraft is built for **AIGC workflows**: assets are generated, not uploaded. You orchestrate image / video / TTS / BGM generation by running bundled scripts, then record the lineage in `project.json`. ## Working with the viewer The viewer is the exploded 3D timeline rendering of `project.json`. It is the user's source of truth for what's currently selected, what the playhead is on, and what they're pointing at. Four channels link the three actors (you, the user, the viewer): ### Reading what the user sees Every user message arrives wrapped in `<viewer-context>` and (if the user just clicked / dragged / seeked) `<user-actions>`. Read them before you act. Typical clipcraft payloads: - `<viewer-context>` — `selectedClipId`, `selectedAssetId`, `selectedTrackId`, `playheadTime` (seconds), `composition.duration`, the active asset's metadata. Use this to disambiguate a vague request like "try another take" — there's almost always a clip selected that tells you which one. - `...