AI Brand TwinMagnetic Messaging Framework

How do we make our brand guidelines machine-readable so our AI tools can use them?

Greg Rosner

By Greg Rosner

Founder of PitchKitchen · Author of StoryCraft for Disruptors

· 7 min read

Hero image for How do we make our brand guidelines machine-readable so our AI tools can use them?

TL;DR

Making brand guidelines machine-readable is a rewriting job, not a file-conversion job. Turn descriptions into decisions: every rule needs a trigger, an action, a real example, and a condition it can fail. Split the document into named units carrying one decision each, so a tool can fetch the ICP without loading the color palette. Add the half most brand books skip, which is who you're for, who you're not for, what you refuse to say, and what you believe your competitors don't. Then serve it from an endpoint your AI tools query mid-draft. A model can't pick a position you never took.

You rewrite them from descriptions into decisions, split those decisions into named units a machine can fetch one at a time, and give every rule a condition it can fail. The file format is the last step and the smallest part of it. Converting a brand PDF into JSON gets you a JSON file full of adjectives, and "confident but approachable" still gives a model nothing to check a draft against.

Most brand guidelines were built to stop a designer from stretching the logo. They were never built to be queried at 4pm on a Thursday by a rep who's mid-draft on a renewal email and needs to know what your company actually claims. That's the gap you're closing, and it's a writing job before it's a technical one.

What does machine-readable actually mean for brand guidelines?

Every rule has to carry a trigger, a decision, and a way to be wrong. A model reads "we're bold and human" and has nowhere to go with it. It reads "never open a cold email with a compliment about the prospect's funding round" and can enforce that against the sentence sitting in front of it. One is a mood. The other is a standard.

Here's the check we run on every line. Would two smart strangers, working in separate rooms, apply this rule the same way? If they'd both flag the same violation, a model will too. If they'd argue about it, the model guesses, and it guesses differently every time it's asked.

Why can't ChatGPT just read the brand book we already have?

It can read it. Reading was never the constraint. Paste all 40 pages into a chat window and the model will summarize them back to you beautifully, then write something generic anyway.

Three things break. The document describes a personality instead of taking positions, so the model fills the positions in from its training data, which is every other B2B company on the internet. It arrives as one undifferentiated blob, so retrieval hands back the color palette when someone asked about the buyer. And nothing in it is forbidden, so the model has no grounds to refuse a single sentence.

That last one does the most damage. We've written before about why AI-written copy comes out sounding off-brand, and the pattern underneath is always the same. The model never learned what you'd refuse to say.

How do we test the guidelines we already have?

Run these six before you rewrite a word. They take an afternoon and they tell you exactly which half of the document is doing work.

The testAsk this about your guidelinesWhat a fail looks like
Failure testCan this rule be broken in a way you could point at on a page?"Confident but approachable." Nobody can fail it, so nobody can enforce it.
Unit testCan a tool fetch one answer without loading the whole document?One 40-page PDF. Ask for the ICP, get the color palette.
Refusal testDo the guidelines name who you're not for and what you won't say?No disqualifiers, no kill list. The model has no grounds to refuse anything.
Example testDoes each rule carry a real before and after from your own writing?Rules stated in the abstract. Models copy examples faster than they follow instructions.
Version testOne owner, one current version, one date on it?Three copies in three Drives. The tool pulls the stale one and nobody notices for a quarter.
Position testDoes the document take a side on positioning, or list the options?"We serve mid-market and enterprise across several verticals." That's a category average, and the model will write like one.

Score it honestly. The visual rules usually pass on their own, because designers write rules that can be violated. The verbal half is where the failures cluster, and the verbal half is the part your team touches every day.

What does a machine-readable rule actually look like?

Take a real one. "Our tone is confident but never arrogant" becomes: claims about outcomes name the customer's number, never ours. Write "cut their onboarding from six weeks to nine days." Never write "industry-leading onboarding." Any sentence claiming a superlative with no customer number attached gets rewritten. Same intent as the original line. One version is a vibe, the other one a machine can run.

Every rule you keep gets four parts: when it applies, what to do, one real example pulled from your own writing, and one counter-example you actually shipped and regret. The counter-example earns its space because models pattern-match on examples faster than they obey instructions.

Then name the units. Positioning, the ICP with its disqualifiers, competitive truth, proof points, vocabulary, the kill list, format specs. One decision per unit, retrievable on its own. That split is what separates a voice guide your team and your AI will follow from a voice guide that lives in Drive and gets opened twice a year.

When we built the Test Kitchen, the MCP server behind our own site, the unit split was the entire job. The Magnetic Messaging Framework goes out as 31 named section templates. The Brand Signal Score goes out as 19 named criteria, each one a pass or fail a machine can apply without reading the other eighteen. Neither number is decoration. They're a count of separately answerable questions, and that count is what machine-readable means in practice.

What's missing from almost every brand guideline we read?

The half that decides anything. Logo clear space, hex codes, a paragraph about tone, maybe an approved boilerplate. Then nothing about who you're for, who you're deliberately not for, what problem you refuse to be hired for, or what you believe that your competitors don't.

That missing half is your narrative identity, and it's a different layer from the visual identity your agency delivered. A machine can't pick a side you never took. Ask a model to write your homepage hero off a brand book with no position in it and you'll get the average of your category, because the average is the only thing available to it. Every hollow draft your team has cleaned up this month traces back to that.

Which is why this rewrite never stays a formatting exercise for long. Making guidelines machine-readable surfaces every argument your team quietly never finished. Two people read the same brand book, describe two different companies, and the document let them both be right. A machine reads it and picks one at random. This is the same work behind an AI Brand Twin, and it's why the twin is worth having.

Where do the guidelines live once a machine can read them?

Somewhere your tools reach without anyone pasting anything. In practice that's an endpoint every AI tool queries mid-draft, which is what an MCP server does. We've laid out whether you should build one and how a framework becomes one, so we won't repeat it here.

Serving is the easy half. A team that skipped the rewrite gets a server that distributes unsettled messaging faster and more consistently than before, and that's harder to catch than ordinary drift, because now every draft agrees with every other draft and they're all a little wrong. Fix the document first. The install is a config line.

What this means for you

Open your brand guidelines this week and read them the way a machine would. Count the rules that can be violated in a way you could point at on a page. If that count comes in under ten, what you have isn't a standard yet. It's a mood board with a font section, and no format conversion will change that.

If you want to see what your public narrative currently gives a model to work with, run your homepage through the Brand Signal Score. It scores the 19 things AI engines actually read on a page. And if you'd rather work the rewrite through with other founders doing the same job, the AI Workforce Clinic runs weekly and the first one's free.

Questions People Ask

FAQ

How do I make my brand guidelines machine-readable so AI tools can use them?

Rewrite the descriptive lines as enforceable rules, each with a trigger, an action, one real example, and a condition it can fail. Split the document into named units carrying a single decision each, such as positioning, ICP with disqualifiers, competitive truth, proof points, vocabulary and the kill list. Put one owner and one version date on it. Then serve those units from an endpoint your AI tools can query while someone is drafting.

Is machine-readable the same as converting our brand book to JSON or Markdown?

No. Format conversion moves the same unusable prose into a new container. "Confident but approachable" is exactly as unenforceable in JSON as it is in a PDF, because a model has no way to test a draft against it. Structure matters, but only after the rules themselves carry decisions a machine can apply and fail.

What belongs in machine-readable brand guidelines that isn't in a normal brand book?

The narrative identity layer. Who you're for, who you're deliberately not for, the problem you refuse to be hired for, what you believe that competitors don't, and the language you'll never use. Standard brand books cover the visual identity and a tone paragraph, which leaves a model to invent every position it needs, and it invents your category's average.

Do we need an MCP server, or is a shared document enough?

A shared document works if your team reliably opens it mid-draft, and most teams don't. An MCP server removes that step by letting Claude, ChatGPT, Cursor and Copilot pull the current rules while writing. Serving is the easy half though. A server built on unsettled messaging distributes the confusion faster and makes it look consistent, which is harder to catch than ordinary drift.

Want this kind of thinking shipping for you?

If the rewrite keeps stalling because your team can't agree on the positions every rule depends on, the file format was never your problem. The 90-Day Magnetic Messaging Sprint is where those arguments get finished and written down as decisions, and decisions are the only version a machine can enforce.

That's the 90-Day Magnetic Messaging Sprint. One quarter, one fixed price: we extract your story, build the Magnetic Messaging Framework and your AI Brand Twin, then ship the website and sales enablement that run on it. $25K–$45K fixed for the quarter, and you own all of it at the end.

About the Author

Greg Rosner

Greg Rosner

Founder, PitchKitchen · Author of StoryCraft for Disruptors · Creator of the Magnetic Messaging Framework™

Greg is a B2B messaging therapist for growth-stage CEOs ($5M-$75M). He helps founders extract the truth they've been hiding from themselves, name the villain in their industry, and build the messaging infrastructure that scales their voice through AI. PitchKitchen has worked with 100+ B2B companies across SaaS, healthtech, fintech, cybersecurity, and AI-driven solutions.