Create structured Brand and Business records, understand what each Brand field means, attach tagged references, link the intended Brand to a project, and wire live Brand properties to compatible Flowgen inputs.
Where: Flowgen → Brain → Records → New → Brand or Business; project settings → Brand to link a Brand.
Key ideas
- Brand is structured source data: A Brand includes typed values for written guidelines, design system, logos, mission/audience/tone/emotions, palette roles, typography, separate web/video CSS and HTML examples, and web/video motion.
- A linked Brand is project context: Project settings choose the Brand that grounds Flowgen. Nodes inherit it by default; connect a specific field to a node input when a visible, live Brand pointer is needed.
- Node-level Brand scope is explicit: Every node inherits the canvas-linked Brand by default. A deliberate per-node override can disable Brand, select another user-owned Brand, or narrow which Brand parts are read; it must never silently borrow another project’s Brand.
- References preserve context and assets: Tagged URLs, uploads, images, and digested documents remain references on the Brain item. Use tags and “in use” state to signal relevant sources without confusing them with typed field values.
- Business is a separate record type: Business records hold organization facts and a profile; they do not replace the Brand’s identity/design fields.
Steps
- Open Brain/Asset Browser → Records and create or edit a Brand record. Choose the Brand type rather than a generic data record so the typed fields and Brand-aware readers are available.
- Inspect each populated Brand field and use the correct source: body for written brand rules, design_system for the reusable design-system payload, logo/logo_vector/favicon for their respective identity placements, and mission/audience/tone/emotions for verbal and creative direction.
- Fill palette roles (primary, secondary, accent, background, text) and heading/body/mono font fields with values the project should actually use.
- Keep the web and video masters distinct: web_css/web_html/web_motion describe the website system; video_css/video_html/video_motion describe the video system and motion language.
- In References, attach the relevant URLs/assets/files, title each source, add useful lowercase tags (for example web, video, motion, product, or campaign), add notes, and choose whether each reference is currently in use.
- Open project settings → Brand and link the exact Brain Brand record that should ground this project. Confirm the correct logo, palette, fonts, guideline body, and tagged references are reflected.
- For a node that needs a visible source chip, call connect_brand_field with the target node and named input. Omit field_key to inspect fields that are type-compatible, then bind the exact returned key.
- When a single node needs a different scope, inspect its Brand controls and set brandMode to inherit, none, or custom. For custom, provide the intended user-owned brandRecordId; use list_records/search_records/read_record to verify the exact record first.
- If the node should use only some linked Brand context, set brandParts to a subset of notes, palette, logo, designLanguage, motion, and references. Omit the override to keep the normal inherited scope.
- Read the node again and confirm the source is a live Brand pointer. Do not copy the same Brand prose into a Text input unless the user needs a deliberately flow-specific variation.
- Create a Business record separately for factual company profile details such as business name, industry, website, and organization description.
Brand field reference
- body — written brand rules and usage constraints.
- design_system — structured reusable design-system data; do not flatten it into prose.
- logo, logo_vector, favicon — exact raster logo, exact scalable SVG, and compact browser/app identity.
- mission, audience, tone, emotions — purpose, intended audience, verbal register, and emotional goal.
- primary, secondary, accent, background, text — semantic color roles.
- heading_font, body_font, mono_font — display, reading, and code/data typography.
- web_css, video_css — separate styling masters; web_html, video_html — examples; web_motion, video_motion — authored motion sources.
How Flowgen consumes Brand context
- The selected project Brand is inherited by generation nodes by default.
- brandMode accepts inherit (default), none (no Brand for this node), or custom (a specific user-owned Brand selected by brandRecordId). A custom node scope is an intentional override, not a project-wide relink.
- brandParts optionally narrows context to notes, palette, logo, designLanguage, motion, and/or references. Do not invent unsupported part names.
- Use connect_brand_field when the user wants a visible field-level wire or a specific structured property on an input.
- A reference is a source asset/context item, not a substitute for a structured field or a design-system socket.
- MCP read_record exposes the record fields and canonical brandProperties entries with exact key, label, type, value, and usage.
Tips
- Keep one canonical linked Brand per project when possible; use node-level overrides only for a deliberate exception.
- Use web/video tags and separate master fields so an editor does not apply the wrong surface’s CSS or motion.
Limitations and important notes
- Brand and Business schemas are different; do not assume a similarly named property exists on both.
- A linked Brand does not automatically turn its typed values into individual input chips; use the Brand field binding when the workflow needs a visible field connection.
- Brand fields and references should contain supported facts and approved assets—do not fill empty values with plausible but invented identity details.
Troubleshooting
Project generation ignores an updated Brand value.
Confirm the project is linked to the Brand record you edited, refresh/read the Brand, and check whether the node intentionally overrides the project Brand or narrows its included Brand parts.
A Brand field cannot connect to the node.
Inspect the exact destination input and ask connect_brand_field to list compatible fields. Bind the canonical key returned for that handle rather than guessing from its display label.
The video editor uses website styling or motion.
Check that the linked Brand has the separate video_css/video_html/video_motion master populated and that the relevant references have video/motion tags.
FAQ
How do I upload a logo?
In the Brand editor's Logo field, click Upload to pick a file, or "From assets" to choose one already in your org Asset Browser. You can also paste an image URL.
Do brand colors change my project theme?
No. Brand records store colors as reference metadata on the record; they do not overwrite your project's design-system tokens or brand settings on their own.