The DNA
Purpose and values, personality and archetype, positioning, audiences, messaging, voice and tone by channel, vocabulary, glossary and style rules, and visual rules on the Brand Kit.
Who the brand is, written once and followed everywhere
Write down who the brand is and how it speaks, publish it as versions, and check every piece of copy against it.
Seven typed sections per domain: Core (purpose, mission, vision, promise, story, values), Personality (the 12 archetypes, 3 to 5 traits, five 1-5 sliders), Positioning (statement, differentiators, proof points with sources, competitors), Audience (personas with goals, pains and objections), Messaging (tagline and alternatives, pitch, 10, 25, 50 and 100-word boilerplates with live word counts, pillars, CTAs, a message per persona), Voice and tone (principles, tone and an example for eight contexts, words to use, avoid and replace, glossary, style rules with en-IN, heading case, emoji, rupee and date formats, examples) and Visual rules (shape language, density, imagery, iconography, motion, layout, accessibility target, do and don't). Every field is validated and capped on the server. The team edits one draft that saves as they type with a version per section, so a second person saving the same section gets Reload theirs / Keep mine instead of overwriting; comments per section with @mention emails; a deterministic strength score with what to fill next. Owners publish the draft with a change note into an immutable numbered version, compare any two versions field by field and restore one into the draft. The domain's Brand Kit (logo, colours by role, fonts, radius) is read through the Brand Kits service binding, shown read-only and refreshed daily, with a WCAG contrast checker for every text and background pair and Start from Brand Kits; nothing is written back. The Brand check always uses the published version: rule checks without AI (words to avoid in their forms, replace pairs, glossary spellings, emoji policy, heading case, Oxford comma, Indian number grouping, dates, en-IN spelling), then with Claude scores for voice, vocabulary, messaging, style and clarity, more issues and an on-brand rewrite; the last 50 checks are kept. Claude also writes on-brand variants in eight kinds, drafts sections from a description, the Brand Kit and the brand's own website as a proposal accepted per field, and reviews gaps. The public brand book at /book shows the public sections in the brand's own look with a print stylesheet; it is off until an owner turns it on after a first publish and hidden from search engines by default. Share links at /book/<token> show the whole published DNA, stored as a hash, with expiry, revoke and view counts. GET /api/v1/dna (public sections only while the book is on; every section with an API key or the workspace key), GET /api/v1/dna/prompt (a brand brief of at most 4000 characters for other catalogs' AI prompts), POST /api/v1/check (60 an hour per domain) and the workspace feed; exports to JSON, Markdown, the AI brief, W3C design tokens and CSS variables; webhook brand_dna.published.
What Brand DNA does for you.
Purpose and values, personality and archetype, positioning, audiences, messaging, voice and tone by channel, vocabulary, glossary and style rules, and visual rules on the Brand Kit.
The team edits a draft and comments; the owner publishes a numbered version with a note, compares any two and restores.
A first draft from your website, a score and fixes for any copy, on-brand variants, and a review of what is missing.
A suggested path for Brand DNA. What you can do depends on your access in the app.
Begin from the Brand Kit's voice fields or let Claude draft from your website.
Fill each section with the team, comment, and publish version 1.
Check copy, write on brand, share the brand book, and let other apps read the brand brief.
Live host, inventory, governance, health checks, verification, dependencies and history.
Seven typed sections per domain: Core (purpose, mission, vision, promise, story, values), Personality (the 12 archetypes, 3 to 5 traits, five 1-5 sliders), Positioning (statement, differentiators, proof points with sources, competitors), Audience (personas with goals, pains and objections), Messaging (tagline and alternatives, pitch, 10, 25, 50 and 100-word boilerplates with live word counts, pillars, CTAs, a message per persona), Voice and tone (principles, tone and an example for eight contexts, words to use, avoid and replace, glossary, style rules with en-IN, heading case, emoji, rupee and date formats, examples) and Visual rules (shape language, density, imagery, iconography, motion, layout, accessibility target, do and don't). Every field is validated and capped on the server. The team edits one draft that saves as they type with a version per section, so a second person saving the same section gets Reload theirs / Keep mine instead of overwriting; comments per section with @mention emails; a deterministic strength score with what to fill next. Owners publish the draft with a change note into an immutable numbered version, compare any two versions field by field and restore one into the draft. The domain's Brand Kit (logo, colours by role, fonts, radius) is read through the Brand Kits service binding, shown read-only and refreshed daily, with a WCAG contrast checker for every text and background pair and Start from Brand Kits; nothing is written back. The Brand check always uses the published version: rule checks without AI (words to avoid in their forms, replace pairs, glossary spellings, emoji policy, heading case, Oxford comma, Indian number grouping, dates, en-IN spelling), then with Claude scores for voice, vocabulary, messaging, style and clarity, more issues and an on-brand rewrite; the last 50 checks are kept. Claude also writes on-brand variants in eight kinds, drafts sections from a description, the Brand Kit and the brand's own website as a proposal accepted per field, and reviews gaps. The public brand book at /book shows the public sections in the brand's own look with a print stylesheet; it is off until an owner turns it on after a first publish and hidden from search engines by default. Share links at /book/<token> show the whole published DNA, stored as a hash, with expiry, revoke and view counts. GET /api/v1/dna (public sections only while the book is on; every section with an API key or the workspace key), GET /api/v1/dna/prompt (a brand brief of at most 4000 characters for other catalogs' AI prompts), POST /api/v1/check (60 an hour per domain) and the workspace feed; exports to JSON, Markdown, the AI brief, W3C design tokens and CSS variables; webhook brand_dna.published.
Logo files, colours and fonts belong to Brand Kits; designs belong to Creatives; campaigns and posts belong to Campaigns and Engagement.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
brand-dnas.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.