Project Intent
Capture the spark: the rough idea, the goal, the audience, and where it lands. The clearer the intent, the sharper every frame that follows.
How to use
From a spark to a shippable vibe
VibeBoard turns a rough idea or saved Vault memory into one cohesive visual direction. Work down the eight steps in the rail. Each move builds on the last, and everything exports from a single handoff.
References
Drop the films, photographers, and textures that carry the feeling. Run Analyze (a session + your own API key) to read each one's lighting, color, lens, pace, and mood.
Vibe DNA
The genome. Generate with AI (admin key or your own BYOK key) or create a local draft to grow the palette, mood, lighting, camera, rhythm, and sound everything inherits.
Board Cards
Sequence the beats. Rename, rewrite, reorder, approve, or delete inline, and run the consistency check on any new shot for a fit score and an in-vibe rewrite.
Style Frames
See it before you shoot. Generate a cinematic frame from any board card. Admins use the studio fal.ai key; everyone else brings their own.
Motion Shots
Turn approved cards and frames into motion-ready shot direction. Keep the camera move, pacing, and visual rules attached to the same board state.
Vibe Check
Test whether a new shot still fits. Paste a shot idea, run the check, and use the rewrite when you need the idea pulled back into the approved direction.
Export
Build every output from one board state: Campaign Engine packet, share deck, deck copy, creative prompts, sound notes, Publish to Vault, and a portable project file.
Starting from Vault Recall
- Use Start in VibeBoard. In DVP Vault, open a saved campaign memory, one of its prompt or asset child records, or an approved VibeBoard direction, then click Start in VibeBoard.
- Read the recall strip. It identifies the source record and lineage. The lightweight recall can include up to eight reusable prompts and eight asset links, but never raw campaign package files or embedded data images.
- Start clean with New Project. New Project resets the board in place, clears any recall strip, and returns you to Step 01.
- Branch locally. Build and edit a local draft. The source Vault record remains unchanged; publish only when the new direction is approved.
Where VibeBoard fits
- Campaign OS. See the full VibeBoard → Campaign Engine → DVP Vault workflow at /campaign-os/.
What Export gives you
- Campaign Engine packet. The structured JSON handoff; "Open in Engine" hands it off directly.
- Shareable vibe deck. A self-contained HTML deck to preview, download, or copy as a live link.
- Deck copy & creative prompts. The Vibe DNA and board turned into presentation text and a generation brief.
- Sound & music notes. The sound direction as a music-supervisor and editor brief.
- Publish to Vault. Saves an approved direction and source packet, plus only the references and generated style or motion assets selected for the deck. The public Vibe Check carries its verdict, summary, and strengths, not private critique or internal scores.
- Lineage that survives. Vault returns the created record IDs. The next Campaign Engine handoff carries those IDs and the VibeBoard project/direction/packet lineage so the final campaign dossier can trace back to its source.
- Project JSON. A portable snapshot saved locally or to the cloud.
Sending a deck to a client
- Preview Client Deck first. This shows the board exactly as the client will see it. Check it before the link leaves your hands, because it is what they judge you on.
- Copy Client Link. Minting a link creates a public, expiring address at
/vibeboard/share.htmlcarrying a signed token. Anyone holding it can view the deck without an account, so treat it as public. - Revoke Share kills it immediately. Revoking rotates the project's share secret, so every link you have ever handed out for that project stops working at once. There is no way to expire just one link, and a revoked link cannot be restored: re-share to mint a fresh one.
- Download Deck for offline delivery. A self-contained HTML file you can email or archive, with no link to revoke and no expiry to explain.
Projects, and what happens when two tabs disagree
- My Projects. Signed in, your boards save to the cloud and list here, so you can move between machines instead of relying on one browser's storage.
- Keep Mine. If the same project was changed somewhere else since you loaded it, VibeBoard asks rather than silently overwriting. Keep Mine keeps the board in front of you and discards the other copy, so read the prompt before you answer.
- Apply JSON. Paste a project JSON straight back in to restore a snapshot or hand a board to someone else without the cloud.
- Previous audits. Consistency checks are kept, so you can see whether the direction has been drifting across a run of shots rather than judging one in isolation.