Brand Context Protocol Registryclaimed
Public brand record

Omniva

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

voice/anti-ai.md

---
bcp_version: "0.8"
file_type: anti_ai
parent: https://registry.brandcontextprotocol.dev/omniva-691-staging/.well-known/brand/voice.md
last_updated: 2026-10-06
---

# Anti-AI voice guardrails

These rules are an **inferred editorial layer** built from Omniva's public brandbook. Omniva has not published or approved this list as a prohibition manual.

```yaml
community_reference:
  - url: "https://encodedbrands.ai/.well-known/brand/voice/anti-ai.md"
    rationale: "Encoded Brands maintains a live baseline of common machine-written language patterns."

brand_additions:
  - pattern: "In today's fast-paced world"
    type: opener
    rationale: "Start with the person, parcel, business need, or delivery action instead."
  - pattern: "revolutionizing logistics"
    type: claim
    rationale: "The brandbook favors helpful solutions, care, and closeness over unsupported category disruption."
  - pattern: "seamless end-to-end journey"
    type: claim
    rationale: "Seamless appears in Omniva's vision, but operational copy must still name handoffs, conditions, and exceptions."
  - pattern: "delivering happiness, one parcel at a time"
    type: slogan_extension
    rationale: "Do not pad the published brand idea with a generic advertising cadence."
  - pattern: "more than just a delivery"
    type: structure
    rationale: "Name the relationship, service, or act of care directly."
  - pattern: "from doorstep to destination"
    type: range_construction
    rationale: "A rhyming range can hide the actual route, service, or next step."
  - pattern: "magical moments"
    type: phrase
    rationale: "The brandbook allows subtle gift-like care but warns against loud Christmas connotations and extravagant surprise."
  - pattern: "your trusted logistics partner"
    type: unsupported_claim
    rationale: "Show trust through a kept, scoped promise or factual service description."
  - pattern: "green delivery"
    type: environmental_claim
    rationale: "Name the initiative, emissions boundary, geography, method, and reporting period."
  - pattern: "world-class, best-in-class, industry-leading"
    type: comparative_claim
    rationale: "Comparatives require a defined category, period, method, and current evidence."
  - pattern: "excessive exclamation marks or emoji chains"
    type: mechanics
    rationale: "Enthusiasm must not reduce clarity or trust."
  - pattern: "humor in delay, damage, loss, complaint, safety, or privacy copy"
    type: context_mismatch
    rationale: "Care and respect take precedence when something has gone wrong."
```

## Structural checks

- Do not open with an abstract claim about connection when a concrete customer need is available.
- Do not stack “care,” “joy,” “seamless,” and “sustainable” into one sentence without a specific service or proof point.
- Do not repeat “delivering happiness” in the headline, first paragraph, and close.
- Do not make every parcel a literal gift or every courier a Santa figure; the brandbook calls for subtle branding.
- Do not use lowercase at the expense of proper names, legal text, accessibility, or local-language rules.
- Do not use a playful headline to soften a material limitation.
- Do not invent delivery times, coverage, prices, tracking states, customer results, partnerships, quotations, certifications, or sustainability outcomes.

## Revision test

Before publishing, ask: Is the line useful? Does it sound warm without becoming saccharine? Is the promise within Omniva's control and supported for this market? Could the humor make a worried customer feel dismissed? Replace generic warmth with one clear action wherever possible.
Domainomnivagroup.com
Registry handleomniva-691-staging
Published2026-10-06 · 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.