Your brand context leaves with you.
Brand libraries inside a single design tool or model vendor work well inside that product. Your assistants are spread across several products. A BCP is plain markdown at a well-known path, so any tool that can fetch a URL can read it.
Three ways to run it.
| Self-hosted | Registry | Both | |
|---|---|---|---|
| Where files live | Your domain at /.well-known/ | registry.encodedbrands.ai/{handle}/ | Same bytes in both places |
| Signed publication | Your choice | Every publication Ed25519-signed | Registry copy signed |
| MCP delivery | You build it | Included | Included |
| Domain verification | Your domain is the source | Free optional DNS verification | Domain plus Registry attestation |
| Cost | Hosting you already have | Public record free. See pricing. |
Encoded publishes its own BCP both ways: at encodedbrands.ai/.well-known/brand.md and on the Registry.
Leaving.
Download the package at any time. The files keep working wherever you host them. The paid Registry layer has to earn renewal through trust and operations, not lock-in.