Asset Management

Every subtab in the Marketing module produces assets. A blurb is an asset. A tagline is an asset. A KDP description is an asset. A query letter is an asset. A social post is an asset. Every piece of generated or hand-written marketing copy gets stored in the project as a persistent, versioned, searchable asset that you can come back to, edit, duplicate, archive, or delete. The Marketing module isn’t a collection of one-shot generation tools — it’s a real content management system for your book’s marketing copy. The asset management layer is what makes this work, and it’s the same across every subtab. You learn it once and it applies to every kind of marketing content you’ll ever produce in Ishvana. This page is the reference for that shared layer.

The ten asset types

Every asset has a type that determines which subtab generates and displays it. The ten types:

Type	What it is	Where it’s created
Blurb	Full-length marketing copy, usually 100-200 words	Copywriting
Short Blurb	Condensed version for ads and cards, 30-80 words	Copywriting
Tagline	One-line hook	Copywriting
Elevator Pitch	Brief verbal-format pitch, 1-3 sentences	Copywriting
Logline	Industry-standard single-sentence story summary	Copywriting
Series Description	Multi-book overview, 75-150 words	Copywriting
Book Description	Amazon-style product description with HTML formatting	KDP & Metadata
Social Post	Platform-specific social media content	Social Media
Query Letter	Agent submission letter with personalization slots	Query Letters
Keyword List	Ad platform keyword research results	Ad Keywords

Each type lives in the same underlying asset table but with different metadata schemas. A social post has a platform field and a character count constraint. A blurb doesn’t. A query letter has personalization slots per-agent. A tagline doesn’t. The type determines which fields are available and which subtab can edit the asset.

Status lifecycle

Every asset has a status that reflects where it is in the editorial workflow:

Draft. Initial or in-progress. The asset exists but isn’t ready to ship. New assets default to Draft.
Final. Committed and ready to use. You’ve reviewed it, it’s the version you’re going with, you’re not still iterating.
Archived. Old or no-longer-relevant. Kept around in case you want to revive it but filtered out of default views.

Status is editable at any time. Move a Draft to Final when you’ve approved it. Move a Final back to Draft if you want to iterate further. Archive old versions when you’ve moved on but don’t want to delete them entirely.

The status system is lightweight — there’s no complex approval workflow, no required reviewers, no gates that prevent promotion. It’s a label that helps you organize, nothing more.

Version history

Every asset tracks its own version history. When you save a significant edit, the previous version is preserved as a snapshot. You can browse earlier versions, see the deltas, and restore any previous version if a recent edit made the asset worse.

Version history matters for marketing content specifically because you iterate on the same copy many times. You write a blurb, you refine it, you refine again, you let a beta reader see it, you get feedback, you change a sentence, you change it back, you cut a paragraph, you restore it. Without version history, you’re working blind — you can’t see what changed, you can’t revert, you can’t compare. With version history, every iteration is preserved and the “best” version is whichever one you picked, not whichever one happens to be the current state.

Version snapshots are created:

Automatically on save after a significant edit (the system detects meaningful changes vs. trivial ones).
Manually when you click “Save Version” from the asset’s toolbar. Useful for pinning a specific state before trying a big revision.
Automatically when a subtab regenerates the asset (the previous generation is preserved before the new one replaces it).

Browse versions from the asset’s right-side panel. Click any version to see its content. Click “Restore” to make that version the current state, pushing the previous current state into the version history as a new snapshot.

Managing assets

The Marketing module’s sidebar has an asset list showing every asset in your current project, grouped by type. You can:

Create assets via the “New Asset” dropdown, organized into four groups: Copy (blurb, short blurb, tagline, elevator pitch, logline, series description), Social (social posts), Queries (query letters), Keywords (keyword lists). Book descriptions are created from the KDP subtab directly since they’re KDP-specific.
Rename an asset by double-clicking its title inline. The rename applies immediately and the asset’s metadata updates.
Right-click for context menu. Every asset has a right-click menu with: Rename, Duplicate, Delete, Change Status, Export, and Copy Content.
Duplicate an asset to create a variant you can edit independently. Useful when you want to try a different approach without losing the original.
Delete an asset. Confirmation prompt. Deletion is permanent — version history is destroyed along with the current version.
Search across all assets using the sidebar search box. Matches against asset title and content, filters the sidebar list in real time.
Filter by type or status using the filter chips above the sidebar list. Filters compose — “Taglines + Final” shows only finalized taglines.
Subtab-aware filtering. When you’re on the Copywriting subtab, the sidebar auto-filters to copywriting-related asset types. Switching to the KDP subtab auto-filters to book descriptions. You can override the filter if you want to see all asset types at once.

Search and filter

The sidebar search is plain text matching against title and content. It’s fast because it runs against the local SQLite database, not against any external service. Type a query and the list narrows in real time.

Filters stack:

Type filter. Show only blurbs, only taglines, only query letters, etc.
Status filter. Show only drafts, only finals, only archived.
Date range. Filter by creation date or last-modified date.
Book filter. If you have multiple books, filter to assets for a specific book.

A common filtered view is “all Final blurbs for Book One, created in the last 90 days” — a specific slice for a specific task.

Assets can be exported in a few formats:

Copy as plain text. One-click copy of the current content.
Copy as Markdown. Formatted with any basic markup preserved.
Export as file. Save the asset to a text file on disk.
Bulk export. Select multiple assets and export them as a single file with sections per asset. Useful when assembling a press kit or sharing multiple assets with a collaborator.

There’s no direct “share to URL” or “publish” action because that’s the job of the channels the assets feed into. The Copywriting blurb goes into the KDP listing manually. The query letter gets sent via email. The social post gets pasted into the platform. Marketing assets are your working state; the channels they feed are where the actual publication happens.

Cross-subtab visibility

Every subtab can see every asset in the project, regardless of which subtab created it. The filtering just defaults to showing assets relevant to the current subtab. This matters because marketing decisions often span subtabs — the blurb you wrote in Copywriting feeds the KDP description, which feeds the Amazon Ads copy, which feeds the social posts. Being able to see all of them in one list helps you keep the voice consistent across channels.

What asset management isn’t

Not a review or approval workflow. No sign-offs, no required reviewers, no gates. The status system is an organizational label, not a workflow state machine.
Not a publishing pipeline. Assets live in Ishvana. Actually publishing them happens on the channel side — you copy copy out of Ishvana and paste it into KDP or Amazon Ads or Twitter.
Not multi-author collaboration. Assets are single-author by default. Version history tracks your own iterations, not multiple collaborators.
Not cloud-synced. Assets live in your local project data. If you want them on another device, sync the data directory.

What’s next

Marketing Brief The shared context that every asset-generation subtab reads from.

Copywriting The primary subtab where most asset types are generated.

KDP & Metadata Where book descriptions and KDP-specific asset types live.