Compiled Brand Truth
The approach we like for our own brand and clients is portable, made up of specifications and structured files—markdown, JSON, and a few well-organized databases—that can easily be handed off and dynamically updated to always reflect the current messaging and visual identity for use in most tools and formats.
Think of it as a compiled Brand Truth. A single reference that includes both the visual identity manifest—design tokens with governance metadata, compliance checks, pattern libraries—and the verbal architecture: narrative elements, application rules, messaging hierarchies with deployment conditions. Prior to compilation they’re both alive as independent, updatable governing sources of truth for their respective domains, and importantly, they cross-reference each other. When the visual identity changes, the verbal layer knows. When a key message gets updated or a key proof point is contested, and those changes are approved by whoever is in charge of such things for your brand, compile the changes and push to your favorite shared file destination for folks and machines to grab from when firing up the content engine.
“Compiled” means the operational version isn’t a living document that people edit in real time—that’s how you get drift. It’s a system that recompiles when specific events trigger it: new evidence, a narrative gaining market acceptance, or new visual elements approved by the brand team.
I don’t think this is the only way to solve the problem. But the problem is real: brand identity stored in static, split-brain containers that aren’t referenced while AI tools generate at scale.
Interface agnostic by design
As things evolve and the best tool for each job tends to shift each week, it makes sense to have, as part of your strategy, an interface agnostic approach to on-brand generative AI. The compiled brand system should be portable, not locked into one system.
I think it’s pretty cool to think about individuals on teams being better equipped to tell a well-informed story and communicate it visually while staying on brand. Further, to have a reliable way to update that governed source of truth when what was true yesterday gets disrupted by better robots, zombies, or inflation. And, to actually then apply it to whatever anyone on the team is making.
I’d love to connect with other folks who are working on this stuff and share ideas. That’s the premise of this series. Over four posts, we’ll walk through the structural problem, the architectural solution, the proof that it works, and a practical blueprint for building it with tools you already have.