DVP Vault — How To Use

01 What the Vault is

DVP Vault stores the reusable memory behind your campaigns: projects, assets, references, tools, prompt recipes, and finished packs. It is the layer that answers "what tools exist, what's approved, what can Campaign Engine use right now?"

It does not replace Campaign Engine. Campaign Engine builds the campaign outputs; the Vault stores and assembles the source material those outputs are built from.

02 The layout

The app is one screen, three columns:

• Left — Filters & Health: filter by type and status, quick type buttons, the Campaign-ready preset, and a live Health panel.
• Middle — Items: a searchable, sortable list of every record.
• Right — Detail, Source Packet, Workspaces, and the Add/Edit form: inspect a record, gather a packet, save/load workspaces, and create or change records.

The top bar holds Reload Seed, Export JSON, Import Vault JSON, and How To Use.

03 Browsing & searching

1. Use Item type and Status dropdowns, or the quick type buttons, to narrow the list.
2. Type in Search vault to match across title, summary, tags, linked items, location, and notes.
3. Change Sort to order by recently updated, title, or type.
4. Click Campaign-ready tools to show only tools that are active/approved and flagged for campaign use.

04 Reading a record

Click any item to load it in the detail panel. Every record shows status, last updated, location, tags, owner, priority, campaign use, and whether it is a source of truth. Three record types add a tailored section:

Tool card

Tools show a short claim, long description, primary CTA, URL, campaign angles, and related prompts — everything you'd want when pitching a tool in a campaign.

Prompt recipe

Prompt recipes show the model target, use case, inputs, and the full prompt template in a copyable block (see section 7).

Asset preview

Assets show a preview image plus kind, rights, and whether they're approved for campaigns.

05 Add, edit, duplicate, delete

1. Fill the Add Item form: type, status, campaign use, priority, owner, source-of-truth, asset fields (kind, rights, preview path, approved-for-campaigns), title, summary, tags, linked items, location, and notes.
2. Click Add To Vault to save.
3. To change a record, select it and click Edit — the form fills with its values and the button becomes Save Changes.
4. Duplicate makes a draft copy; Delete removes a record (with confirmation).

06 Source Packets → Campaign Engine

A Source Packet is the bridge to Campaign Engine. Gather the records a campaign needs, then copy them in a Campaign Engine-ready format.

1. Select a record and click Add To Packet (or Add All Campaign-Ready Tools to grab every campaign-ready tool at once).
2. Give the packet a title and an objective so the downstream brief is clear.
3. Click Copy For Campaign Engine to copy a structured reference with Reference links, Reference assets, Required copy, Must include, Avoid notes, and Visual direction — paste it straight into Campaign Engine's References stage.
4. Copy Packet copies a plain-text packet; Export Packet saves it as JSON; Clear empties the tray.

07 Prompt recipes

Prompt recipes are reusable, copyable instructions for an LLM. Open a recipe to see its template, then click Copy Prompt Recipe to copy the full recipe (model target, use case, inputs, template, and expected output). Recipes added to a Source Packet carry their template text along with them.

CinePrompt can save approved prompt recipes into DVP Vault. Consistency Keeper can save both prompt recipes and references. Those saves land as browser-local draft records first, then you can export Vault JSON when they are approved for the canonical repo data.

08 Campaign Workspaces

A workspace is a saved campaign — a named collection of records you can reopen later.

1. Build a Source Packet, give it a title, then click Save Packet As Workspace.
2. To reopen, pick a workspace from the dropdown and click Load Workspace — its records repopulate the Source Packet and its title/objective return.

09 Campaign Engine round trip

The strongest workflow is a loop, not a one-way export.

1. Use DVP Vault to gather approved tools, assets, prompt recipes, and references into a Source Packet.
2. Click Copy For Campaign Engine, then paste that packet into Campaign Engine's References stage.
3. Build the campaign in Campaign Engine with Local Draft, AI Brain, or manual handoff.
4. Edit slides, export creative tool packs, and review safe areas.
5. Click Save Pack To Vault in Campaign Engine's Export stage.
6. DVP Vault receives the finished campaign as a pack record containing the editable project, copy pack, creative tool pack, Runway scene pack, and Remotion scene plan.

10 Import a Campaign Engine project

There are two ways to close the loop: the newer Save Pack To Vault button from Campaign Engine, or a manual JSON import.

1. In Campaign Engine, click Download Project JSON.
2. In the Vault, click Import Vault JSON and choose that file. The Vault detects a Campaign Engine project automatically.
3. It becomes searchable records: one project, one pack, an asset for each slide image, and a prompt for the captured LLM prompt — all added alongside your existing items.

11 Health checks

The Health panel keeps the Vault honest. It flags missing titles or summaries, missing locations on assets/projects/packs, broken linked references, duplicate titles, assets without rights, prompts without an expected output, and campaign-ready items without tags.

1. Read the issue counts in the Health panel.
2. Click Show issues only to filter the list down to records that need attention.

12 Where your data lives

• Browser storage: your edits save to this browser's localStorage automatically.
• Seed files: canonical starting data lives in data/dvp-vault.seed.json, data/dvp-tools.seed.json, data/dvp-prompt-recipes.seed.json, and data/dvp-workspaces.seed.json.
• Reload Seed restores the starting library (replacing what's in the browser).
• Export JSON saves a dated backup (dvp-vault-YYYY-MM-DD.json); Import Vault JSON loads a backup or a Campaign Engine project.
• Offline: opening index.html directly (file://) works — the app falls back to a built-in copy of the seed since browsers block reading the JSON files over file://. Serve the folder to load the JSON files live.

13 Tips & FAQ

• "Preview not found" on an asset? Add the real image to the assets/ folder at the path in the asset's preview field.
• Keep titles tight. Short titles read better everywhere and avoid the "title too long" health-style problems downstream in Campaign Engine.
• Mark your sources of truth. The Campaign Engine reference text leads with source-of-truth and high-priority records under "Must include."
• Back up before big changes. Export JSON first; Reload Seed and imports replace the current library.
• Lost work? Your data is in this browser. Use a consistent browser/profile, and export regularly.

DVP Vault · DynamicVibe Productions · Back to the Vault