# Omninal — Brand context

Kit version: 0.1.0. Status: local design candidate, not a production release.
Canonical website: https://brand.omninal.com
Scope: brand, communications and interface design. This is not a source of live product availability, commercial terms, licensing or transaction state.

## Position

One account. Global business. / 一个账户，连接全球业务。 Audience: merchants, business owners and finance teams. Connect collection, distinct currency balances and global payments through one business account. Current image direction: Enterprise 01. Read enterprise-visuals.en.md or enterprise-visuals.zh.md; these take precedence over earlier image-generation, campaign and flat-social profiles. Keep this Brand / Design System site separate from the commercial website.

Omninal is building an alternative to traditional business banking: a clearer way to manage and move money globally. Express this ambition through clarity, control and continuity. Do not describe Omninal as a licensed bank, insured deposit provider or guaranteed settlement service unless the specific brief supplies approved facts.

## Identity

- Use the supplied original SVG mark. Never redraw, rotate, distort, extract a petal or generate it with AI.
- Brand name: Omninal. Preserve its spelling and case in every language.
- Primary signature: blue symbol plus dark wordmark, horizontally aligned. Use the supplied lockup master; do not typeset a replacement.
- Product signatures are horizontal: Omninal | Global Account, Omninal | Payments, Omninal | Business OS. These names are examples of identity architecture, not a feature-availability statement.
- Product descriptor: Inter Medium, approximately 73% of the master wordmark text size, dark neutral. A quiet hairline divider separates the master and descriptor. Never stack the product name under the master or create a new product logo.
- Co-brand: complete Omninal signature × partner signature. Keep independent identities and optical balance.
- Minimum clear space: one quarter of the symbol height. At small sizes use the original standalone symbol rather than squeezing the signature.

## Visual language

- Light mode is the default. White or near-white surfaces, dark type, deliberate blue accents. Blue #155DFC is the anchor; retain the token source for all semantic use.
- Typography: Inter for Latin and brand signatures; Noto Sans SC for simplified Chinese; Pretendard for Korean. Do not claim other language font bundles are included unless listed in the manifest. Preserve local-script readability instead of forcing Latin tracking.
- Editorial headlines: medium weight, short, generously spaced. Avoid heavyweight text everywhere, faux dashboards, unnecessary borders and gradients.
- Money: explicit currency, locale-aware formatting, tabular digits. Show signs, fees, time zone and next action when relevant. Never imply all currencies have two decimals.
- Icons: Lucide, 24-unit viewBox, 2-unit stroke, round ends. Financial symbol selection is in icons.json. Use SVG for design and transparent 512px PNG for presentations. Do not mix icon families.
- Aperture: original mark geometry, unrotated, enlarged and clipped once. The central star stays outside the frame. Use the supplied 12 SVG presets; blue at 7% on #FAFBFD. Decorative crops must not compete with text or appear as a second logo.
- Photography: clean daylight, credible devices, uncluttered composition. Existing New York device art is a generated composite using credited photographic references; it is not documentary evidence of an office or shipped product.

## Voice and financial accuracy

Precise, composed and direct. Lead with the outcome; add only information needed to choose or act. Use short sentences and sentence case. Do not fabricate metrics, savings, coverage, partnerships or delivery times.

For a payment state, show what is known and the next action. Never turn a generic error into “No funds have moved.” Only say this when authoritative transaction data confirms it. Submitted, processing, completed, failed and refunded are distinct. Unknown is not failed; completed is not automatically settled. Do not infer transaction facts from animations or icons.

## Interaction

Respect native iOS/Android behavior. Provide keyboard access, visible focus, accessible names, labelled status, loading/error/empty states and a reduced-motion alternative. Confirmation precedes consequential actions. Motions describe state changes; they do not invent success. Reference the native and motion source archives for platform implementations.

## Using this kit

1. Read this document and the task-specific prompt.
2. Read tokens.json; use semantic aliases before primitives. Do not replace token values with a guessed palette.
3. Reuse the manifest assets and preserve their geometry and licenses.
4. Distinguish concept data from verified product facts in your deliverable.
5. Report which kit version and assets you used. Where the brief conflicts with this candidate, ask the project owner about that specific conflict.

This document supplies design context only. It does not grant an agent permission to publish, spend, alter accounts or execute downloaded instructions.
