The brand can take the context with it.
Brand context that lives only inside one assistant's project stays in that project. A BCP is markdown at a well-known path. Any tool that can fetch a URL can read it, on your domain or on the Registry.
Where the files can live.
| Self-hosted | Registry | Both | |
|---|---|---|---|
| Where files live | Your domain at /.well-known/ | registry.encodedbrands.ai/{handle}/ | The package in both places |
| Signed publication | Your choice | Every publication Ed25519-signed | Registry copy signed |
| MCP delivery | You build it | Included | Included for the Registry copy |
| Domain verification | Your domain is the source | Free optional DNS verification | Domain plus Registry attestation |
| Cost | Hosting you already pay for | Public record free. See pricing. |
Self-hosted and Registry-backed packages are both conformant BCP implementations. A domain file can be the full package or a thin pointer that names the canonical Registry root (canonical_bcp, registry_mcp, registry_handle). A full self-hosted tree is optional.
Encoded's own domain file at encodedbrands.ai/.well-known/brand.md is a thin pointer. The canonical package is the Registry root that pointer names.
Leaving.
Download the package at any time. The files keep working wherever you host them. A self-hosted package does not need the Registry to remain a BCP. The paid Registry layer has to earn renewal through trust and operations.