Core concept

Brand profiles

A brand profile is the canonical record of your workspace's voice and audience. Every agent in the pipeline reads from it — the planner, the generator, the verifier and the regen step that escalates to human review.

Fields

• Voice tone: one of formal, friendly, bold,expert, playful. This biases prompt templates and the verifier's strictness.
• Target audience: free-text description (≤ 500 chars). The more specific, the better the plan agent can pick angle and references.
• Brand pillars: 1–10 topic anchors. Both the planner and the verifier insist on at least one pillar showing up in the final piece.
• Image provider: flux2_pro (default) or nano_banana.
• Regen cap: 1–5. After this many failed verifications the item moves torequires_human_review.

Where it lives

The data lives in Postgres under tenant-isolated rows (RLS-enforced). The 3D knowledge graph at /brand/graph reads it directly from Postgres — relations between pillars, audience segments and feedback signals from the learning loop — with no separate graph database.

How to edit

Initial creation happens during signup at /onboarding/scan. After that, edits live across the Brand Hub: name, pillars and company story at /brand/identity, voice tone at /brand/voice, target audience at /brand/audience, and image provider / regen cap at /brand/visual.

Propagation

Changes take effect on the next pipeline run; running pipelines keep the snapshot they started with so a single run is consistent. The Tenant Brain graph is updated asynchronously from the learning loop within ~30 seconds.