Brand Packs
The machine-readable categorised dataset of brand data points and assets that every Wavecast rendering engine reads to produce on-brand output.
What is a Brand Pack?
The modelIt reads top-down — the Brand Pack feeds the Templates, and the Templates feed every output.
Brand Pack contents
8 componentsEight components make up a pack — seven brand primitives plus the assembled Templates layer. Each is its own categorised slice of the dataset.
Logos
Every lockup and mark, with the rules of use bound to each.
Colours
The semantic colour set — tokens, values and on-fill pairings.
Typography
The type role system — fonts, weights and metrics per role.
FormingArtwork
Brand artwork and backgrounds — the graphic furniture of a brand.
Icons
The icon library — one consistent set, styled to the brand.
FormingIllustrations
Illustration style and assets — characters, spots and scenes.
Elements
Brand-level UX objects — buttons, badges and primitives.
FormingTemplates
Brand-locked compositions, saved into the pack for reuse.
- Logos, Colours and Typography are live references; Artwork, Illustrations and Templates are forming.
- Icons and Elements are surfaced from the Library — referenced here, not duplicated.
- The model is the dataset, not a fixed list of files — new components can be added as the brand surface grows.
Who has a Brand Pack
Brand Packs can be stored at the Account, Workspace or Event level. They are available and portable — each level inherits the one above and overrides only what it needs.
Examples
PlaceholdersReal Wavecast packs — to be built out and dropped in here.
Moody’s
Account-level pack.
Awaiting brand dataION Analytics
Account-level pack.
Awaiting brand dataFIPP Congress
Event-level pack.
Awaiting brand dataWhat it is — and isn’t
DraftA working articulation, to refine.
- A live dataset — structured, categorised and queryable by any engine.
- The single source of truth for a brand’s assets and rules.
- Versioned and re-skinnable — change a value, every output follows.
- Portable and scoped — stored at Account, Workspace or Event level, and movable between them.
- Rules included — clearspace, misuse, pairings, tone — not only files.
- A static PDF or slide deck of guidelines.
- A DAM — a folder of files someone has to hunt through.
- A manual lookup or copy-paste exercise, asset by asset.
- Locked to one design tool or one output format.
- A creative brief — it governs the brand, not campaign messaging.
- Data first: the Brand Pack is a dataset. The Notion registries (Colour, Typography…) are its canonical, queryable form; this site mirrors them.
- Captured, not only sourced: designed templates are saved back into the pack, so it holds both the primitives and the compositions assembled from them.
- One lever: re-skinning a client or event is a change to values, not a re-draw — every engine’s output follows automatically.
The machine-readable brand — a categorised dataset of assets, templates, conventions and rules that replaces static PDF guidelines and the DAM. Constituent values mirror the Notion registries; not edited here.