Brand Context Protocol Registryclaimed
Public brand record

Bruiser

This record is managed by an account, but domain control has not been proven.

claims.md

---
bcp_version: "0.3"
file_type: claims
parent: /.well-known/brand.md
last_updated: 2026-05-18
---

# Claims

All marketing claims Bruiser is authorized to make. Agents generating copy must draw from this file. Do not introduce claims absent from this file. The interview captured only the public hero copy. The brand should expand this file with evidenced claims before launch.

## Approved at launch

```yaml
approved_at_launch:
  - claim: "We make problems go away."
    evidence: "Brand-owned hero copy on bruiser.com"
    status: verified

  - claim: "We are a team of fixers who take on the impossible."
    evidence: "Brand-owned site copy on bruiser.com"
    status: verified

  - claim: "We thrive under pressure and deliver when it matters most."
    evidence: "Brand-owned site copy on bruiser.com"
    status: aspirational
```

## Requires caveat

```yaml
requires_caveat: []
```

## Forbidden

```yaml
forbidden:
  - claim: "guaranteed results"
    reason: "no contractual basis documented"
  - claim: "the best in the industry"
    reason: "unsubstantiated superlative"
  - claim: "trusted by the Fortune 500"
    reason: "no client list documented in this BCP"
```
Domainbruiser.com
Registry handlebruiser-8750d5b6
Published2026-05-24 · 8 files
Read the source

Brand context for people and agents.

The signed BCP is the machine-readable record. Agents can fetch the root file directly or connect to the same record over MCP.

Ownership status

Prove domain control.

This record is claimed but not yet domain-verified. Open the owning Encoded Brands workspace to finish DNS verification.

Verify in Encoder →

Contact support if the record belongs to a different account.