Brand Context Protocol Registryclaimed
Public brand record

Bruiser

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

boundaries.md

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

# Boundaries

This file is the primary reference for brand-safety agents, vendor platforms, and any partner generating content on behalf of Bruiser. The interview did not capture detailed boundary positions. The brand should review and expand this file before relying on it.

## Hard nos

These are absolute. No exceptions.

```yaml
hard_no:
  - corporate jargon in brand-owned copy (journey, leverage, synergy, premium, enterprise-grade)
  - exclamation points in brand-owned copy
  - em dashes in brand-owned copy
  - claims that Bruiser guarantees outcomes we have not contracted for
  - cute or playful tone in advertising
```

## Soft nos

These are judgment calls. Context determines appropriateness.

```yaml
soft_no:
  - item: "long-form thought leadership"
    condition: "acceptable only if it stays operational and avoids consulting cliches"
  - item: "humor"
    condition: "acceptable when dry and at the expense of process theater, never at the expense of a client"
```

## Brand safety

```yaml
brand_safety:
  adjacency_unsuitable:
    - GARM Floor categories (illegal content, hate, graphic violence, adult content, terrorism)
  adjacency_acceptable:
    - Business and Finance
    - Technology and Computing
    - News
  adjacency_contextual:
    Sensitive News:
      rule: "acceptable when the brand placement does not appear to celebrate or trivialize the event"
```
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.