Brand Context Protocol Registryclaimed
Public brand record

Omniva

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

visual.md

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

# Visual guidance

This file transcribes Omniva's live public brandbook. Use the current brandbook assets and examples for production. Do not redraw the logo, synthesize the licensed typeface, or treat a public download as permission for every use.

## Authority and gaps

```yaml
visual_authority:
  status: brand_published
  observed_on: 2026-10-06
  sources:
    - "https://www.omnivagroup.com/brandbook/logo/"
    - "https://www.omnivagroup.com/brandbook/typography/"
    - "https://www.omnivagroup.com/brandbook/colors/"
    - "https://www.omnivagroup.com/brandbook/photography/"
    - "https://www.omnivagroup.com/brandbook/illustrations/"
    - "https://www.omnivagroup.com/brandbook/graphic_elements/"
    - "https://www.omnivagroup.com/brandbook/layout/"
  not_confirmed:
    - "license terms for every downloadable logo, font, photograph, illustration, and template"
    - "font files or redistribution rights for TT Wellingtons"
    - "a text transcription of the minimum logo sizes shown only in the brandbook's raster diagram"
    - "complete WCAG results for every published color combination"
    - "motion specifications"
```

## Logo

The symbol repeats one shape four times around a central square. Omniva says the form symbolizes movement and happiness. The wordmark uses the same friendly geometric sans-serif character as the identity and retains the lowercase “o” from the previous identity.

```yaml
logo_usage:
  generation_policy: official_assets_only
  generation_instructions: "Do not draw, trace, typeset, approximate, or hallucinate the Omniva symbol, wordmark, wordmark-with-slogan, lockup, or pattern. Use a current official asset from the live logo page and confirm rights."
  available_forms:
    - "symbol"
    - "wordmark"
    - "wordmark with slogan"
    - "horizontal or vertical lockup"
  official_download_page: "https://www.omnivagroup.com/brandbook/logo/"
  clear_space: "Keep a safety zone equal to the letter O on every side, following the official diagram for the chosen asset."
  minimum_size: "Use the exact digital or print minimum in the current official raster diagram; no numeric value is inferred here because the page does not publish it as text."
  approved_color_families:
    - "orange"
    - "deep black"
    - "sun yellow"
    - "berry purple"
    - "monochrome black or white"
  forbidden_modifications:
    - "non-proportional stretching"
    - "new lockup combinations"
    - "adding curves or imitating the brand pattern with the logo"
    - "positions outside 90-degree angles"
    - "drop shadows"
    - "outlined logo versions"
    - "undefined logo colors"
    - "using the logo as a photo mask"
```

For photography, choose an official white or deep-black variant that is legible on the actual image. The brandbook illustrates approximately 30% deep-black or white overlays when the image needs more contrast. Test the final composition; do not rely on the example caption alone.

## Color

Omniva calls its palette bold, friendly, and distinctive. Orange, white, and black do most of the work. Sun yellow and berry purple increase brand volume; secondary colors support interfaces, buttons, and notifications and must not become more prominent than the primary colors.

```yaml
color:
  primary:
    - name: "Orange"
      pantone: "Pantone 1505"
      hex: "#FF6600"
      rgb: "255/102/0"
      cmyk: "0/64/100/0"
      ral: "2004; 2008 for parcel machines and letterboxes"
    - name: "White"
      hex: "#FFFFFF"
      rgb: "255/255/255"
      cmyk: "0/0/0/0"
      ral: "9003"
    - name: "Deep black"
      pantone: "Pantone Black"
      hex: "#000000"
      rgb: "0/0/0"
      cmyk: "0/0/0/100"
      ral: "9004"
    - name: "Sun yellow"
      pantone: "Pantone 7549"
      hex: "#FFBC01"
      rgb: "255/188/1"
      cmyk: "0/28/100/0"
      ral: "1003"
    - name: "Berry purple"
      pantone: "Pantone 517"
      hex: "#E3C6E4"
      rgb: "227/198/228"
      cmyk: "1/22/0/0"
  secondary:
    - { name: "Grey", hex: "#F4F4F4" }
    - { name: "Dark grey", hex: "#2D2D2D" }
    - { name: "Peach", hex: "#FBE6D9" }
    - { name: "Pale yellow", hex: "#FCEED0" }
    - { name: "Pink", hex: "#FAEAFD" }
    - { name: "Green", hex: "#73CA62" }
    - { name: "Pale green", hex: "#DAFED6" }
  rules:
    - "Use orange, white, and deep black as the dominant system."
    - "Use sun yellow and berry purple for additional brand volume and accents."
    - "Use secondary colors carefully and precisely; never let them become more prominent than the primary palette."
    - "Use only primary brand colors for the graphic smile elements."
    - "On orange, the graphic-element guidance permits pure white; on deep black, use white outlines."
    - "Test text, icons, controls, focus states, and overlays for contrast in the actual size and context."
```

## Typography

```yaml
typography:
  primary:
    family: "TT Wellingtons"
    foundry: "TypeType"
    rights_note: "The brandbook identifies the family but does not grant font redistribution rights. Obtain and license it through an approved Omniva workflow."
    supported_scripts_as_published:
      - "Western Europe"
      - "Central/Eastern Europe"
      - "Baltic"
      - "Turkish"
      - "Romanian"
      - "Cyrillic"
  fallback:
    family: "Arial"
    role: "system typeface when TT Wellingtons is unavailable"
  hierarchy:
    large_headline: "TT Wellingtons Medium, approximately 4.4x, 118% line height"
    subheadline: "TT Wellingtons Medium, approximately 2x, 118% line height"
    accent: "TT Wellingtons Medium, uppercase, approximately 1x, 136% line height, 12% character spacing"
    button: "body-text style in Demi Bold or a different brand color; use only as needed"
    body: "Medium, 160% line height; examples show 1x and 0.8x sizes"
  rules:
    - "Use lowercase for customer messages to create a friendly feel where language and context permit."
    - "Maintain clear size contrast between headline, subheadline, and body."
    - "Do not set long body copy in uppercase, italics, or Demi Bold."
    - "Use italics and Demi Bold only as short accents."
    - "Use traditional lining numerals for pulled-out data and oldstyle numerals in running text as shown by the brandbook."
    - "Do not fabricate TT Wellingtons with a similar geometric sans. Use Arial when the licensed primary face is unavailable."
```

## Photography

```yaml
photography:
  overall: "Natural, warm, joyful, and credible, with a few bright red or orange accents."
  portraits:
    - "Use natural light and realistic emotion rather than saccharine expression."
    - "Include small Omniva-orange accents unobtrusively."
    - "Avoid harsh shadows and overexposure when studio lighting is necessary."
  environments:
    - "Use a semi-documentary view of nature, cities, and towns."
    - "Prefer warm tonality and medium exposure without overly dark shadows."
    - "Sunny scenes are welcome, but realistic rain and overcast weather are valid when warmth or small orange accents remain."
    - "Choose clean compositions with one focal point and limited background detail."
    - "When people are contextual rather than the subject, the guide allows distance without identifying features."
  joy:
    - "Show intimate, close life moments with a light-hearted, warm, cozy feel."
    - "Orange accents may be bold."
    - "Use medium-to-high image contrast without overexposure or harsh high-contrast shadows."
  avoid:
    - "stock photography"
    - "staged or acted-out sets"
    - "over-the-top emotion or poses"
    - "holiday cliches"
    - "unnatural group poses"
  source: "https://www.omnivagroup.com/brandbook/photography/"
```

The photography page contains context-dependent guidance on showing faces versus distant, non-identifying figures. Apply the rule for the intended category and obtain consent and usage rights; do not invent a universal people-photography rule.

## Illustration

```yaml
illustration:
  character: "Light, simple, and balanced between technical drawing and fluid organic lines."
  source_basis: "Start from a reference photograph."
  construction:
    - "Use 1 pt pen-tool lines with round caps and corners in Adobe Illustrator, as published."
    - "Keep most lines separate for a loose feeling; round selected corners for smoothness."
    - "Use mostly black linework, with primary-color accents when needed."
    - "Displace color shapes slightly and retain some unfilled space."
    - "For standing figures, the guide specifies a black radial-gradient foot shadow at 30% opacity."
    - "Simplify small-scale figures, especially facial detail."
  usage:
    - "Use illustration when photography cannot express the idea, when material needs relief from photography, or when subtle attention is required."
    - "Keep illustrations to no more than 30% of social content."
    - "Do not mix photography and illustration in the same post, item, section, or slide."
  avoid:
    - "chalk, watercolor, or other artistic line effects"
    - "dense, detailed linework"
    - "using illustration as the main way to show real customers and emotions when photography is available"
  source: "https://www.omnivagroup.com/brandbook/illustrations/"
```

## Graphic elements and icons

```yaml
graphic_elements:
  careful_hold:
    meaning: "Care and precision around every entrusted shipment."
    behavior: "Adapt elements derived from the Omniva symbol around the content area."
  stack_of_smiles:
    meaning: "Satisfied customers and the Omniva team."
    behavior: "Smiles may vary in color, movement, and size; stacked versions remain smile-side up."
  encompassing_link:
    meaning: "Connections across the stages between expectation and outcome."
    behavior: "Build rhythmic color sequences with no more than three branches from one connection."
  icons:
    style: "simple, functional, geometric, and easy to understand"
    published_recommendation: "Use the Orion Icon Library when suitable; develop additions only in the demonstrated vocabulary."
    rights_note: "Confirm the Orion asset license and Omniva approval before production use."
  generation_boundary: "Do not reconstruct these elements from prose. Use current official artwork or an Omniva-approved designer."
  source: "https://www.omnivagroup.com/brandbook/graphic_elements/"
```

## Layout and brand volume

```yaml
layout:
  foundation:
    - "Favor left-aligned content."
    - "Use two letter-O widths as the rule-of-thumb text margin; depart only when the composition requires it."
  lower_volume: "Separate wordmark from symbol; use restrained content and elements over brand-color fields or photography."
  medium_volume: "Let adaptable symbol elements support the composition while text remains predominantly left-aligned."
  medium_with_twist: "Use dynamic smile angles less often, to enliven the system rather than define its core."
  high_volume_stack: "Open the symbol into orderly or freely orchestrated stacks of large and small smiles."
  high_volume_special: "Reserve colorful linked smiles, symbol patterns, and other deviations for unique, thoughtfully designed cases while retaining the established layout principles."
  source: "https://www.omnivagroup.com/brandbook/layout/"
```

## Production checklist

1. Obtain the official asset and confirm its rights, language, format, and current version.
2. Use TT Wellingtons only when properly licensed; otherwise use Arial.
3. Select a published palette combination and test real contrast.
4. Choose one image language per unit: photography or illustration, not both.
5. Keep customer copy friendly and legible; do not force lowercase where it damages meaning.
6. Use graphic elements from official artwork, not a redraw.
7. Check the logo's O-based safety zone and the official minimum-size diagram.
8. Confirm that the finished piece does not imply Omniva approval of this demonstration.
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.