FetchBuzzScoopOchoSeeti
Snapshots

Every brand's recipe, written down, with Seeti signing only the foot

Being built
  • Every read makes the partner a Brand Book, shareable with people and AI tools.
  • The partner's colour, type and photos lead: no chilli, no steel, no Bakbak One.
  • In files an AI reads, there are no characters and no kitchen words.
  • Seeti signs once: Cooked by Seeti. Over to you.
  • House recipe is Seeti's word for the book and for the memory page.
32pixel sign off mark
Your call

Use house recipe as one word for both the Brand Book and the memory page?

Brand · 4.13 · Seeti

The Brand Book we give brands, Seeti

DraftLast checked 2026-10-26Owner Param

Answer

Every read makes a partner a Brand Book of its own brand, shareable with any person or AI tool, and this settles what it holds and exports today and how Seeti frames it without ever dressing the partner's brand in Seeti's kitchen.

Today

What it holds

Chapter What is in it
Story Who the brand is, from its own pages brew/public/brand-book.js:35
Look and kit Logo, colours with roles, fonts read from the font files brew/public/brand-book.js:35; memory brew-brand-book-guards
Voice and Words Voice traits, its own lines, words it uses, the never say list brew/public/brand-book.js:35
Products Products, price steps, offers, the whole catalogue on a deeper page brew/public/brand-book.js:35; brew/brand-book-read.js:18
People and Proof Personas, ratings, review lines, press and founders brew/public/brand-book.js:35-36; brew/brand-book-read.js:5
The numbers Counts from the read brew/public/brand-book.js:36
What the brand publishes Its own ads, posts, films and photos, by deliverable, best first brew/public/brand-book.js:36; brew/brand-book-read.js:27-31
Playbooks, Where it shows up, Rivals, Rules Format playbooks, channels, rivals, rules for claims, people and AI brew/public/brand-book.js:36

How it is built

  • The read builds it from public evidence only, plus one Gemini vision call for story, voice, words, claims and look. Every AI line names its evidence; quoted lines are checked in code; no evidence leaves the field empty. brew/brand-book-read.js:1-12
  • Saved as brands//brandbook-read.json, at book version 6. brew/brand-book-read.js:12, 18
  • Uploads sit over the read, the team's edits over those. Members see everything, a share sees the read plus non private edits, public sees the read only. brew/jam2/brandbook.js:6-10, 132-158
  • Every maker reads it: drafts, cards, statics and the Studio take its prompt and creative blocks. brew/jam2/brandbook.js:10; memory brew-brand-book
  • Meta winners, uploads and team rules are members only and never in share or public. memory brew-brand-book-guards

What it exports

Route What it is
//brand The book as a read only page, no login brew/brand-kit.js:4; brew/server.js:948-950
//brand.md An AI ready brand prompt for ChatGPT, Claude or Gemini brew/brand-kit.js:5
//brand.json The whole book as data, each line with its source brew/brand-kit.js:6
//llms.txt The index an AI agent reads first brew/brand-kit.js:7
//brand.pdf The book as a PDF brew/server.js:941; brew/brand-book-routes.js:93
//brand-kit.zip All of it plus W3C tokens, colors.css, an .ase palette, logos, references by format, product photos, and project notes for Claude and ChatGPT brew/brand-kit.js:8-9, 99-101

How it looks

  • The book is dressed in the brand itself: its colour and logo on the cover, its heading font on every chapter, its colour chips. The product's chrome stays quiet around it. brew/public/brand-book.js:1-3
  • Two visible lines still name the old product: How Brew writes for the brand, and Brew makes new pieces. brew/public/brand-book.js:145, 153
  • Guards run on every Brand Book deploy, for every brand. brew/test/brand-book-guards.test.js; brew/tools/audit-brand-book.mjs; memory brew-brand-book-guards

Tomorrow

  • v1, Stays: the name is Brand Book on every button and tab, the plain word. brand-directions/cooker/system.md section 3
  • v1, New: around the button, Seeti calls it the house recipe written down: every kitchen has its own way of doing things, and Seeti writes it down. brand-directions/cooker/brand.html b3
  • v1, New: the line when the book is ready: Your brand book. Fresh off the stove. Share it with anyone. brand-directions/book/content/h2.js:137
  • v1, Changes: the book opens from Share your brand book in What we know about you, and AI search links to it as the fix for answer gaps. brand-directions/book/content/h2.js:142
  • v1, Stays: the partner's brand leads every page: their colour, their type, their photos. No chilli, no steel, no Bakbak One inside the book.
  • v1, New: Seeti appears only as the 32 pixel sign off at the foot of the shared page, Cooked by Seeti. Over to you. Never on the cover, a chapter, a colour chip, a product or a rule. brand-directions/docs2/data/dirs.json cooker lines.signoff; brand-directions/cooker/system.md section 5
  • v1, New: in brand.md, brand.json, llms.txt, the PDF and the kit zip, no character and no kitchen words. Files an AI reads stay plain.
  • v1, Changes: the two visible Brew lines become plain words with no product name: How we write for the brand, and New pieces are made from the ones that match.
  • v1, New: the never say list is a rule for every draft. Seeti may scold an idea that breaks it, never the person who wrote it. brand-directions/cooker/system.md section 4
  • v2, New: every post the brand approves to schedule is made from the book. brand-directions/book/content/h2.js:118
  • v3, New: the book marks which of the brand's best work did best, once the product measures. Seeti's plate checker line can point to it. brand-directions/book/content/h2.js:118; brand-directions/cooker/character.html c10
  • v4, Stays: ads within rules follow the book's rules for claims. No new chapter needed.

How we do it

  1. Before any Brand Book deploy, copy a brand's bucket JSON and private files into a folder and run the audit and the guards:
cd /Users/param/Documents/ChatGPT/brew && node tools/audit-brand-book.mjs DIR && node --test test/brand-book-guards.test.js
  1. Add a check and a guard test for every new issue class found, so it never returns for any brand.
  2. Never leak members only data into share or public views.
  3. Check the shared page shows the brand's colours and type, with Seeti only in the sign off slot.
  4. Bump the book version in brand-book-read.js when the shape changes, so every book rebuilds.

Numbers

Metric Definition Where measured Status
Books built Brands with a brandbook-read.json from their latest read Bucket listing of brands/*/brandbook-read.json Proposed
Shares Opens of //brand, .md, .json, llms.txt, .pdf and .zip Server request logs Proposed
Empty fields Share of book fields left empty for lack of evidence audit-brand-book.mjs output Proposed
Guard failures Guard tests failing before a deploy, target zero test/brand-book-guards.test.js Exists

Open

  1. Does Seeti sign the shared Brand Book page at all? Proposal: yes, the 32 pixel sign off only, and nothing in the files an AI reads.
  2. Seeti's word for it: house recipe is also the word for What we know about you. Use one word for both? Proposal: yes, house recipe for both, since the Brand Book is that memory written down.
  3. Should the free kit for brands only read, not on the product, carry the sign off? Proposal: yes, the same 32 pixel sign off, so the gift says who made it.
Sources
  • brew origin/main a559de6: brand-book-read.js:1-18; jam2/brandbook.js:1-12, 132-158; brand-book-routes.js:93; brand-kit.js:1-9, 89-114; server.js:936-950; public/brand-book.js:1-5, 34-37, 145, 153; test/brand-book-guards.test.js; tools/audit-brand-book.mjs
  • memory brew-brand-book; memory brew-brand-book-guards
  • brand-directions/book/content/h2.js:104-145 section h-11 brand-book
  • brand-directions/cooker/brand.html b3; brand-directions/cooker/character.html c5
  • brand-directions/cooker/system.md sections 3, 4, 5

Source file content/brand/the-brand-book-we-give-brands.cooker.md · For agents: Markdown · JSON