What is the Brand Brain?
The Brand Brain is a Digital FTE's memory of the business it works for: what the company does, who it serves, how it speaks, what it claims and never claims, its products and their facts, and the rules the manager has set. It lives in the Memory tab of the workspace, and every item shows its provenance: from onboarding, from a document you provided, from a connected system, or learned from a pattern in your approvals.
It is per property, so an FTE managing two websites holds two Brand Brains. And it is shared across the FTEs working on that property, so a fact corrected once is corrected for all of them.
Why does provenance matter?
Provenance matters because it tells you how much to trust an item and where to fix it if it is wrong. An item from onboarding is something you typed; an item from a document is something you provided; an item learned from approvals is an inference the FTE drew from your decisions, which may or may not be what you meant.
Inferred items deserve the closest reading. An FTE that notices you always send back drafts mentioning a competitor may infer a rule never to mention competitors, which might be right or might be an over-generalisation. The provenance chip shows it is inferred, and you confirm or correct it.
How do you review it at hiring?
Review the Brand Brain fully at hiring, before the first proposals. The first-run wizard pre-fills it from what the platform already knows and from the documents you connect, and the FTE's early drafts will be built on it. Read every item, correct what is wrong, remove what should not be there, and add the rules that are missing.
This is the highest-leverage hour in the first week. A wrong product fact in memory becomes a wrong claim in every draft until corrected; the fact gate will catch unsourced claims, but a claim sourced from wrong memory passes.
- Read every item and its provenance
- Correct wrong facts; remove items that should not be there
- Add missing rules: tone, prohibited topics, protected audiences
- Confirm inferred items or replace them with explicit rules
How do you maintain it?
Maintain it by correcting items as you notice them in proposals. A draft that gets a product detail wrong is a memory item to fix, not just a send-back; fix the memory and the next draft is right. When the business changes, such as a new product, a new price, or a new voice guideline, update the Brand Brain once and every FTE on that property inherits it.
Confirm it quarterly. The workspace prompts a quarterly confirmation, where you read the memory again and confirm or correct each section. Businesses change quietly, and a memory that was right in January can be wrong by June without anyone having decided anything.
What should never be in it?
Nothing that should not be a basis for the FTE's work. Personal data about individuals has no place in a brand memory; customer records belong in the connected systems with their own access controls, not in memory. Confidential plans the FTE should not write about should not be there either, unless the rule that it never mentions them is there with them.
Treat the Brand Brain as a document a new hire would be given on day one: everything they need to represent the company, nothing they should not know, and every fact something you would defend. That is the standard, and the provenance chips are what make it checkable.
What does a labelled example of a Brand Brain entry look like?
As a labelled example, one entry in a Search Visibility FTE's Brand Brain reads: the product is priced by metered work in tokens from one organization wallet with no per-seat charge, with the provenance chip from onboarding and a link to the pricing page, confirmed by the manager on a stated date. Another reads: never claim a specific payback period or savings percentage, with the chip inferred from approvals and the three send-backs it was inferred from listed, awaiting confirmation. A third reads: the brand does not comment on competitors by name, with the chip from a document and the brand guidelines file cited.
Reading those three, the manager confirms the first, promotes the second from an inference to an explicit rule with a click, and checks the third against the guidelines. Each confirmation is logged. An entry with no provenance chip does not exist, because every item came from somewhere, and an entry the manager has not confirmed shows as unconfirmed so that the quarterly review knows where to look. The whole memory for a property reads in half an hour, which is the cost of knowing exactly what the FTE believes.