---
bcp_version: "1.1.1"
file_type: onboarding
parent: /.well-known/brand.md
last_updated: 2026-09-30
audience: ["humans", "IT / admins"]
note: "Map of Encoded surfaces related to this demonstration package. Not agent instructions."
---

# Onboarding map: Encoded demonstration package for Firefox

Companion to the Package map in `brand.md`. Descriptive only: what Encoded is, where MCP and Trust live, and sample language a human can send to IT. **Not directions to an agent.**

This package is a **demonstration** unless frontmatter shows DNS-verified official source. Not endorsed by Firefox by default.

## What Encoded is / isn’t

| Is | Isn’t |
| --- | --- |
| Brand Context Protocol (open spec) + Registry (signed publish, HTTPS + MCP delivery, free DNS verification) | An AI writing app that generates campaigns |
| Encoder = compiler / on-ramp for a portable BCP package | A replacement for a design system or CMS |
| Self-hosted BCP = first-class | “Must host on Registry to be real” |

## Surfaces tied to this package

| Surface | Where |
| --- | --- |
| Package root | `https://registry.brandcontextprotocol.dev/firefox-8df36a3b/.well-known/brand.md` |
| Registry MCP for this handle | `https://registry.brandcontextprotocol.dev/mcp?customer_handle=firefox-8df36a3b` |
| Example page (if live) | `https://encodedbrands.ai/examples/firefox` |
| Product site | https://encodedbrands.ai/ |
| Trust Center | https://encodedbrands.ai/trust |

Daughter files for this brand are listed on the package root under `daughter_files`.

## MCP connector context

Many team / enterprise AI products gate **custom MCP connectors** behind an **admin**. Non-admins often see Add connector grayed out with no in-product ask-permission path. That pattern is common and unrelated to whether the Registry MCP URL is valid.

Encoded does not claim native BCP adoption or endorsement by Anthropic, OpenAI, Google, Microsoft, or other LLM vendors. Custom MCP is user-configured and plan/admin gated.

## Sample email a human can send to IT / admin

**Subject:** Encoded Registry MCP for Firefox brand context

Hi,

We’re evaluating Encoded Brands’ Brand Context Protocol so our AI tools can share one source of brand truth (voice, visual, claims, boundaries).

Could you add this **read** MCP connector for our workspace?

- MCP URL: `https://registry.brandcontextprotocol.dev/mcp?customer_handle=firefox-8df36a3b`  
- Public package: `https://registry.brandcontextprotocol.dev/firefox-8df36a3b/.well-known/brand.md`  
- Product / trust: https://encodedbrands.ai/ · https://encodedbrands.ai/trust  

Scope we care about: fetch public brand context for drafting. Not auto-publish or unattended edits to brand files.

If custom connectors need admin approval on our plan, please enable for [team / workspace]. Happy to jump on a short call.

Thanks,  
[Name]

## Trust Center notes (for humans)

https://encodedbrands.ai/trust  

Only link sections that are actually published. Signature ≠ domain control; claimed ≠ DNS-verified; Registry Certified ≠ “human reviewed every claim.” No invented SOC 2, ISO, or pen-test status.

## Free vs later (factual, not pricing)

- Public package readable at the Registry URL without MCP.  
- Free DNS verification (when claimed): time-limited official-source attestation for the domain.  
- Paid / Certified (when sold): gated companions, seats, named audit of authenticated gated access. Public files remain public.

Commercial offers live on Encoded’s current pricing / commerce surfaces. This file does not state prices.

## After claim + DNS verify

Demonstration pitch on the package root is replaced with a short functional map. Provenance stays accurate. “Not endorsed / assembled by Encoded from public sources” stays only while true.