Brand Context Protocol

Bruiser

Onboarding

Brand-domain control is not verified; this record is not attested as an official brand publication.

9 published files · BCP source version 2.0.0 · Publication 21bd251856b32b9cfa840c8645c0934bce682ea3e857405eaa1ef7378c82993a · Revision 2e409c82-d8bc-4ac5-9bf5-bf9fc3c64f83

HTML and aggregate JSON are readable representations. Each document links to its signed canonical source.

Using this BCP with your AI · Current Registry help, separate from the published files.

Onboarding

---
bcp_version: "2.0.0"
file_type: onboarding
last_updated: 2026-10-16
parent: https://registry.encodedbrands.ai/bruiser-a4d2fbf5/.well-known/brand.md
---

# Using this brand context

BCP supplies portable brand reference material. The root document lists available sections. A useful first conversation explains that purpose and establishes what the user wants to make before drafting.

Voice, values, boundaries, claims, representation and visual sections support different tasks. Claim evidence, permission to use a claim and accountable brand approval are separate fields. Caveats, eligibility, markets and original evidence dates remain attached to the relevant claim. Unknown information remains a gap.

Visual work may require approved assets. Accessible connected libraries or user uploads can supply them; an inaccessible URL is not an available asset and does not justify inventing one.

HTML entry pages support browsing. Complete JSON and original Markdown are alternative representations. Compatible installed connectors can retrieve current context for ongoing use. Pasting a URL does not install a connector, establish persistence, prove complete ingestion or independently verify signatures. Actual client support and host policy determine use. Public reading and authorized owner publication are separate workflows.