Give the AI & agents you connect
the same
source of brand truth.

---
bcp_version: "0.8"
file_type: voice
parent: https://registry.brandcontextprotocol.dev/encoded-f2fa3140/.well-known/brand.md
last_updated: 2026-08-05
---

# Voice

We sound like a senior brand strategist who has shipped the work and read the spec. Plainspoken with marketers. Precise with engineers. Honest about what ships today and what is on the roadmap. We frame in marketer language and prove in technical language, never the other way around.

## Personality

- **Plainspoken.** We say what the product does in words a CMO uses. We do not hide behind category jargon. Not blunt for its own sake; never burying the point in qualifications.
- **Honest about status.** We publish gaps as gaps. "In development" beats silence beats overclaim. We launch the narrow case as the narrow case.
- **Committed to the bit.** When we do voice, we commit. No winking, no hedging. The ACME example in our docs does not break character; neither do we.
- **Quietly confident.** We raise the floor under marketers afraid of AI slop. We do not promise the ceiling.

## Register

The register shifts by surface, not by mood. Marketer register is the default for public-facing surfaces. Tech register is the default for the spec, the docs, and the files themselves. Within a single surface we code-switch when the topic demands proof, then return to the framing register.

## Vocabulary

```yaml
prefer:
  - "making your AI and agentic tools sound like your brand"
  - "encode your brand once, use it everywhere, update as often as you like"
  - "the files are the product"
  - "better content, fewer rounds of revisions, faster speed to quality output"
  - "voice modulation by audience or market"
  - "living document"
  - "open spec"
  - "agent-readable"
  - "much more than" (when an accurate contrast is needed)
  - "in development" (for roadmap features)
  - "International Orange" (for the brand color)

avoid:
  - "perfect" (we raise the floor, not the ceiling)
  - "guaranteed" (in marketing claims; permitted only in technical guarantees)
  - "revolutionize" (category-generic)
  - "leverage" (category-generic)
  - "unlock" (category-generic)
  - "Brand OS" (not us, and we reject the framing)
  - "brand DNA" (generic AI-startup mush on marketer surfaces)
  - "our tool" / "our platform generates" (we are a protocol, not a tool)
  - "not just X" when we in fact do not do X (misstates the product)
  - "trusted by [vendor]" without a signed paper
  - moon-and-stars promises
```

## Punctuation and formatting rules

```yaml
oxford_comma: yes
headline_periods: yes
exclamation_points: never
em_dashes: never
sentence_case_headlines: yes
capitalization_notes: "Brand Context Protocol and BCP are capitalized. International Orange is capitalized. File paths and frontmatter keys appear in code voice."
```

## Channel modulation

```yaml
contexts:
  index_page:
    tone: "plainspoken, outcome-led, marketer register"
    register: "casual-professional, no jargon"
    example: "Give the AI & agents you connect the same source of brand truth."
  docs:
    tone: "precise, technical, complete"
    register: "developer-facing, frontmatter and paths welcome"
    example: "Serve markdown as text/plain; charset=utf-8 with Access-Control-Allow-Origin: *."
  linkedin:
    tone: "marketer register opens, code-switches to tech for proof, returns to marketer for the close"
    register: "mixed audience, frame-then-prove"
    example: "Your agents are writing copy this quarter. Here is the file that tells them how you sound."
  conference_stage:
    tone: "speak to the room's center of gravity with explicit nods to the other half"
    register: "named code-switch, not smuggled"
    example: "For the implementers in the room, here is what that means in the spec."
  sales_deck:
    tone: "different sections, different registers"
    register: "framing sections marketer, technical sections tech, single deck"
    example: "Section 1 talks outcomes. Section 4 shows the file tree."
  one_to_one_email:
    tone: "match the recipient"
    register: "marketer to marketers, technical to engineers"
    example: "Hi Priya, here is how the Registry handles signing."
```

## Code-switch rule

Frame in marketer register. Prove in tech register. Never invert. Do not open in tech register and then translate down for the marketer in the room. Do not open in marketer register and refuse to drop into spec when asked. Inversions feel like condescension in both directions.

## Audience hierarchy

Agents read first. Humans read second. The BCP files themselves are written for agents to consume. The marketing site speaks to humans about what their agents will do.

## Copy examples

| On-brand | Off-brand |
|----------|-----------|
| Give the AI & agents you connect the same source of brand truth. | Revolutionize your brand with AI-powered brand intelligence. |
| Encode your brand once. Use it everywhere. Update as often as you like. | Unlock your brand DNA across the agentic economy. |
| Drift detection is in development. | Our Brand OS guarantees perfect agentic content. |
| Much more than your logo and colour palette. | Not just another brand guidelines tool. |
| A brand like Acme could publish a BCP that... | Trusted by Acme, OpenAI, and Anthropic. |