Stage 02 — BrandOS
Visual Identity Code + Verbal Identity Code — two halves of brand identity that finally talk to each other. Compiled into one machine-readable operating system.
The Problem
Two systems that never talk
Every brand operates with a split brain. Visual identity has version control, token propagation, and automated compliance checking. Verbal identity has a Google Doc somewhere and good intentions. These two systems are governed separately, stored separately, updated on different cycles, and drift apart under production pressure. The drift is silent and compounding.
// Visual Identity → mature tooling designTokens: { color: "#f44d37", usage: "CTA only" } typography: { scale: "modular", tracking: "-0.02em" } compliance: automated ✓ // Verbal Identity → no standard voice: "a Google Doc somewhere" messaging: "ask Sarah, she knows" compliance: manual review ✗
Visual Code
Your visual system as structured data
01
Design Tokens
Colors, typography, spacing as structured data with governance metadata. #f44d37 becomes “use for CTAs, never as background fill, max 15% of frame area.”
02
Composition Rules
Layout patterns, aspect ratios, grid systems. 1,200+ layout combinations possible via token combinatorics.
03
Anti-Patterns
Hard constraints. No drop shadows. No gradients on light backgrounds. No stock photos. No centered body copy. The rules that protect brand integrity.
04
Asset Library
26 logos, 9 stickers, 64 illustrations — all machine-accessible with usage metadata.
Verbal Code
Your voice as structured data
01
Voice Architecture
Tone, register, vocabulary rules. Authoritative. Clear. Consequential. Peer-to-peer, not vendor-to-buyer.
02
Anchor Vocabulary
44 terms with precise mappings. “Governance” not “guidelines.” “Architecture” not “template.” “Compound” not “accumulate.”
03
Message Architecture
Brand phrases, key messages, value propositions — each with deployment rules and required narrative elements.
04
Persona Routing
How voice modulates per audience. CMO gets strategic framing. Design lead gets Brand-as-Code. Content ops gets workflow proof.
Compilation
Two codes, one operating system
Changes to visual tokens trigger verbal recompile. Changes to verbal messaging trigger visual compliance check. Dependency cascades ensure nothing drifts silently.
12M+
Designs already governed via Canva MCP — machine-readable brand identity is operational, not theoretical.
See what it produces
Engines →