Catalogues

Catalogues are your Organization's reusable creative elements. They are the raw material the campaign matrix is built from, so the same segment, product, or message can drive many campaigns without being retyped.

What works today

The catalogue library works end to end: catalogues with declared fields, catalogue items with descriptions, asset links, and soft-deletes. Importing catalogue items from external sources is covered on the Feeds page.

Catalogues are your lists

A catalogue is a named list you define, like "Segments", "Products", or "Cities". You create as many as you need and order them. A list has to be empty before you can delete it. You can also create one on the spot while connecting a feed, instead of making the list first.

A catalogue also declares its fields: an ordered set of named fields (say Colour, Price) that every item in the list fills. You define them once on the catalogue, reorder them, and hide the ones you do not need on screen (see Hiding a field). Each field can be filled from a feed column and used as a storyboard token, so the same field name flows from the list to the matrix to the script.

Catalogue items are the entries

A catalogue item is one entry in a list. Each item has:

• A name.
• The values for the catalogue's declared fields.
• A description: what the item is, also used to steer the prompts that use it.
• Optional linked assets, for example a product's image.

Editing the fields

The field list has two homes and both edit the same thing:

• The catalogue's Edit dialog, where you set a new list up.
• The Fields button above the item list, which opens the editor as a popover over the list. It keeps your place: the items stay on screen and the scroll position holds, so working through a long schema never sends you back to the top.

Each row leads with the field's label; naming a field is usually all it takes. The chevron on a row opens its settings: the stable key (what a feed column maps onto and a token references), the type, the lookup, and the hide toggle. A collapsed row summarises anything non-default as a small badge, drag the handle to reorder (or focus it and press the arrow keys), and on a feed-sized schema a filter above the rows narrows them by label or key. Every change is local until you press Save fields, so hiding twenty fields is one save and Cancel drops the lot. A click outside the popover leaves it open rather than throwing half-made edits away.

The catalogue's name is renamed where it is read: click it in the panel heading above the item list, type, and press Enter.

Hiding a field

Hide from item views, in a field row's settings, hides that field from the item views. It drops out of the item form and off the field chips on the item rows, and nothing else changes. The field keeps its key, its values, its {{tokens}}, and its feed column mapping, so a hidden field still fills from a sync and still resolves in a storyboard. A crossed-out eye marks a hidden field's row, and the same toggle brings it back.

This is for a feed-sized catalogue: hide the forty columns nobody edits by hand and keep the six that matter on screen. The feed mapper still lists every field, hidden ones included, on purpose, because mapping a column you never want to see in the item form is exactly the case hiding is for.

Lookup fields

A field can look its value up in another catalogue. Point a field at a second catalogue (its lookup catalogue), and the item whose name matches the field's value lends its own description and fields to the storyboard, one level deeper.

Say a Products catalogue has a product_type field holding WALL_LAMP or DESK_LAMP. You keep a second catalogue, Product prompts, whose items are named WALL_LAMP and DESK_LAMP, each carrying a prompt field with a detailed generation prompt. Set product_type's lookup to Product prompts, and the storyboard gains {{Products.product_type.prompt}}, resolving per combination to the prompt of the matching item.

The rules are short:

• Match by name. The value is matched to the lookup catalogue item whose name equals it, ignoring surrounding spaces and letter case. If two items share the name, the oldest one wins.
• A miss uses the value itself. When nothing matches, every dotted token ({{Products.product_type.prompt}} and the rest) falls back to the raw value, so a typo shows up as plain text instead of blocking generation. The miss is flagged in the UI. A matched item that leaves one of its fields empty resolves that token to an empty string, again without blocking anything.
• One hop only. The matched item's own lookup fields do not chain: you get its plain field values, not a lookup of a lookup.

The base token {{Products.product_type}} still resolves to the raw value (WALL_LAMP), unchanged. Because the lookup reads live catalogue facts, editing a prompt in Product prompts changes what an unrendered combination resolves to, never a creative you have already rendered.

Image link fields

A field can be typed Image link instead of plain text. Paste an image's web address into it and, on save, Klyo downloads the image into your asset library as a read-only synced asset and links it to the item, exactly as a feed's image column works. The address stays the field's value, so its {{variable}} keeps resolving to the raw link. The same address is downloaded once and reused across items and re-saves. If the link cannot be fetched or does not point at an image, the save still goes through and the editor tells you which field could not resolve; fix the address and save again. An Image link field cannot also be a lookup field.

Linking assets

You can link one or more assets to a catalogue item, in bulk, and unlink them again. The picker also takes a fresh upload on the spot, including by dragging a file straight onto it, so linking a new product shot does not mean a trip to the asset manager first. If a linked asset is later deleted, the link is marked unresolved so the gap shows rather than disappearing.

Persona brief

An item of an audience catalogue can carry a persona brief: a short strategic one-pager on that segment. Mark the catalogue as holding People in its edit dialog (products and other things never get a persona), then open the item and use Draft with AI at the bottom of the edit dialog, or Write it yourself to start from empty fields. The AI draft works from what the item already says (its name, description, and field values) plus your organization's brand guidelines:

• Snapshot, who this is.
• Tension, the problem they feel.
• Desire, what they want instead.
• Message angle, the line of argument that connects the two.
• Tone notes, how it should sound.

The AI draft works only from the facts on the item, so it invents no demographics or claims, and it writes in the language of the item's own description. You own the wording: the pencil edits any field in place, the provenance line records who wrote the draft and when you last rewrote it, and clearing every field removes the brief. Regenerate replaces the whole brief with a fresh draft, your edits included, and the copy button takes it as text.

The brief is also read where the campaign is written: when the sample combination includes this audience item, idea, storyboard, and ad copy generation carry the brief, so the work is aimed at the person it describes. Rendered videos are never touched retroactively; an updated brief only shapes what you generate next.

Deleting keeps history

Deleting a catalogue item is a soft delete. The item is tombstoned rather than erased, because campaigns, axes, and frozen combination packages may still refer to it. Deep links to a deleted item still resolve, so nothing dead-ends.

How catalogues feed the matrix

In a campaign you add a catalogue as an axis. Klyo then multiplies the axes together to produce the matrix of combination packages. You can use a whole catalogue or a curated subset on any given axis. See Campaigns.

What you can do today

• Create, rename, reorder, and delete catalogues, and declare each catalogue's fields from the Edit dialog or the Fields popover beside the item list.
• Hide a declared field from the item views, leaving its key, values, tokens, and feed mapping as they are.
• Create, edit, and soft-delete catalogue items with field values and a description.
• Search a catalogue by name; long lists page so a feed-sized catalogue stays usable.
• Link and unlink assets, in bulk.
• Generate a persona brief per audience item and regenerate it when the item changes.
• Reuse the same catalogue items across many campaigns.
• Populate catalogue items automatically from a feed.