# 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. --- # Omninal — Enterprise visual standard Edition: Enterprise 01. Status: local design candidate. Language: English. ## 1. One account. Global business. Audience: merchants, business owners and finance teams. A single business account connects collection, currency balances and global business payments. Show account ownership first, the transaction second, geography third. This is a design direction, not a declaration of country availability or settlement speed. This is the current default for enterprise imagery. It supersedes earlier campaign/device/flat-social art direction when they conflict. Legacy assets remain downloadable for reference only. Brand logo geometry, #155DFC primary blue and the existing typography remain unchanged. ## 2. Six image objectives | ID | Communication objective | Role | | --- | --- | --- | | one-workspace | One business account across desktop and mobile | Product workspace | | terminal | Credible, grounded hardware for everyday collection | POS portrait | | merchant-counter | A payment within natural merchant work | Editorial scene | | merchant-account | The merchant sees a USDC receipt in their own account | Receipt study | | global-operations | Global oversight in a real work setting | Enterprise context | | account-architecture | One center connects collection and distribution | Spatial metaphor | Each image has one objective and one focal point. Do not reuse one generic device composition for every claim. ## 3. Image grammar - Light surfaces, daylight, pale stone or architectural glass; use real material texture and contact shadows. Dark hardware is allowed on a light field. - Blue is a purposeful accent or account center, not an all-over wash. Avoid purple/neon, floating coins, miniature cities, globes, decorative holograms and shiny toy objects. - Devices are full-scale tools: credible thickness, seams, docks, screen aspect ratios and legible content. Keep all functional hardware visible. Device concepts are not production hardware specifications. - People work naturally. Avoid staged celebration, impossible hands and portrait stereotypes. AI scenes are illustrative, not documentary customer photographs. - 3D explains consolidation, relationships or direction. Keep one light source and physically consistent depth. Do not derive new logos from the brand mark. - City scenery is context, never proof of regional availability. A country label is a conceptual route, not a coverage promise. ## 4. Three independent layers 1. Image plate: generated environment, materials and concept screens. 2. Product proof: real HTML/native components with explicitly authored account, amount, asset, status and action. The interactive account specimen is the functional reference; generated screens are visual studies only. 3. Brand layout: exact original SVG lockup and editable, localized headline. Never ask an image model to redraw the logo. Keep English and Chinese headlines outside the bitmap. Current photographs contain English concept UI; bilingual exports localize the headline and framing, not every screen pixel. For shipping UI, use localized components rather than the image. Inter / Noto Sans SC are bundled with their licenses. Do not convert Chinese into pseudo-Latin glyphs. ## 5. Financial clarity Keep the amount and asset adjacent: `128.00 USDC`, never bare `128.00` or `$128 USDC`. USDC, USDT and USD are distinct units. Do not sum mixed currencies without a named quote currency, rate source and timestamp. Make pending, received, available and sent explicit. A completed animation does not confirm settlement. Never infer zero fees, instant arrival or country support from a visual. Use fictional balances and label the specimen as an example. ## 6. Motion and spatial presentation Omninal-derived timings: 120 ms control feedback, 180 ms small transitions, 240 ms content changes, 400 ms expressive reveals. Use duration and easing together. Product motion is restrained; expressive spatial movement is reserved for the account story. One narrative animation per section. No scroll hijacking, compulsory pointer tracking or endless decorative loops. Default to static, allow play/pause/replay and keyboard controls. `prefers-reduced-motion` must preserve the complete static meaning. Change state from data, not animation completion. ## 7. Delivery and acceptance Generate a 1536 × 1024 landscape master. Export landscape and 4:5 with the entire image contained, never crop hardware to fill. Logo/headline align to the same margins. Keep text editable; supply PNG, HTML template, raw image, prompt and catalog. Package current standards and image checksums. Inspect every master at full size, verify numbers and hands, then check mobile crop, bilingual headlines, focus and reduced motion. Current machine entry: `/enterprise-visuals/catalog.json`. Prompt set: `/enterprise-visuals/prompts.json`. Download: `/downloads/omninal-enterprise-visuals.zip`. Functional reference: `/en/motion#account-motion`. All URLs resolve against the current host. --- # Omninal — 企业视觉标准 版本：Enterprise 01。本地设计候选版。语言：简体中文。 ## 1. 一个账户，连接全球业务。 面向商户、企业经营者和财务团队。以同一个企业账户连接收款、多币种余额与全球业务付款。先交代账户归属，再呈现交易，最后呈现地域。这是设计方向，不是国家覆盖或到账时效的产品承诺。 本文件是企业影像的当前默认规范；与早期营销、设备、二维社媒规范冲突时，以本文件为准。旧素材仅作为历史参考保留下载。Logo 原始几何、主色 #155DFC 和既有字体不变。 ## 2. 六个出图目标 | ID | 要表达的目标 | 角色 | | --- | --- | --- | | one-workspace | 桌面与移动端属于同一个企业账户 | 产品工作台 | | terminal | 可信、落地、日常可用的收款工具 | POS 特写 | | merchant-counter | 自然经营过程中的一笔收款 | 商户现场 | | merchant-account | 商户在自己的账户里看到 USDC 到账 | 到账研究 | | global-operations | 真实工作环境中的全球业务管理 | 企业语境 | | account-architecture | 一个账户中心连接归集与分发 | 空间隐喻 | 每张图只承担一个目标、一个视觉焦点，不用同一个设备模板解释所有能力。 ## 3. 视觉语言 - Light Mode、自然日光、浅色石材与建筑玻璃；有真实材质和接触阴影。浅色环境中可以使用深色设备。 - 蓝色用于重点或账户中心，不铺满画面。避免紫色霓虹、悬浮硬币、微缩城市、地球、装饰光环和玩具质感。 - 设备是工具：厚度、接缝、底座、屏幕比例合理，内容可读。功能性硬件应完整可见。设备概念不代表量产规格。 - 人物自然工作，不摆拍庆祝、不出现畸形手指。AI 场景是示意，不冒充真实客户照片。 - 3D 用于解释归集、关系与方向。统一光源与空间深度，不把 Logo 拆解成新标志。 - 城市仅是环境；国家标签是概念路线，不代表已开通市场。 ## 4. 三层独立制作 1. 影像层：生成环境、材质与概念屏幕。 2. 产品层：真实 HTML / 原生组件明确制作账户、金额、币种、状态、下一步。账户交互示例是功能参考；生成图中的屏幕只作视觉研究。 3. 品牌层：叠加原始 SVG 标识与可编辑的本地化标题。不得让模型重绘 Logo。 中英标题独立于位图。当前影像的概念屏幕为英文；双语成品翻译标题与版式文字，不代表屏幕像素也已经本地化。正式产品使用本地化组件，不照搬生成图。素材包附 Inter / Noto Sans SC 及许可，不使用伪中文。 ## 5. 金融信息 金额和单位相邻：`128.00 USDC`，不写裸数字或 `$128 USDC`。USDC、USDT 与 USD 是不同单位。没有报价币种、汇率来源与时间，不合计混合币种。明确区分待处理、已收到、可用、已发送。动画结束不代表结算完成。不从视觉推断零手续费、瞬时到账或国家支持。示例使用虚构余额，并标明“示例”。 ## 6. 动效与空间展示 Omninal 派生时长：控件反馈 120 ms，小幅切换 180 ms，内容变化 240 ms，重要揭示 400 ms；时长和缓动成对使用。任务动效克制；空间表达用于账户关系。每区最多一个叙事动画。不劫持滚动，不强制跟随鼠标，不无休止装饰循环。默认静态，可播放、暂停、重播和键盘操作。减少动态效果模式保留完整静态语义。产品状态由数据决定，不由动画结束决定。 ## 7. 交付与验收 生成 1536 × 1024 横版原图。横版和 4:5 成品均完整容纳原图，不为填满画幅裁切设备。Logo 与标题对齐同一边距。文字可编辑，交付 PNG、HTML 模板、原图、提示词和目录，附当前规范与图片校验值。逐张放大检查文字、金额与手部，再检查移动端、双语标题、焦点及减少动态效果。 机器目录：`/enterprise-visuals/catalog.json`。提示词：`/enterprise-visuals/prompts.json`。下载：`/downloads/omninal-enterprise-visuals.zip`。功能参考：`/zh/motion#account-motion`。相对路径均使用当前网站域名。 --- # Marketing task Read brand.md, tokens.json and the asset manifest first. Create an Omninal communication for the audience, channel, dimensions and objective in the supplied brief. Use a light background, one concise headline, one visual idea and one clear next action. Use supplied SVG identity assets. Keep utility links away from the identity lockup. Use the financial icon catalog for meaningful explanations, not ornament. Output the proposed copy, layout and asset filenames. Label illustrative product screens and unverified placeholders. Do not invent performance numbers, approvals, pricing, partnerships, insured status or supported markets. If a fact is missing, omit the claim or identify the specific fact needed. Do not add Product/Company website navigation to brand-system material. For social imagery read image-generation.md. Preserve source credits. Keep logos and final typography as editable overlays; never bake an AI-redrawn logo into the artwork. --- # Sales and presentation task Read brand.md, tokens.json and icons.json first. Build a concise presentation around the buyer's problem, the proposed workflow and the next conversation. One main idea per slide. Use light backgrounds, readable numbers, restrained blue and generous whitespace. Use the SVG financial icons where the slide tool supports them; otherwise use the transparent 512px PNGs. Preserve aspect ratio and consistent visual size. Use source master logos, never recreated text. Keep partner marks distinct. Use only facts, markets, product capabilities and numbers supplied in the brief or an explicitly approved source. Treat screenshots, sample balances and device KVs as concepts. Do not turn the aspiration to replace traditional banking into a licensing or deposit-protection claim. Do not invent customer quotations, guarantees or savings comparisons. Deliver editable slides, source asset references and a short list of any unresolved factual placeholders. Do not publish or send the deck unless instructed. --- # Product interface task Read brand.md, tokens.json and icons.json. Build for the target platform using semantic tokens and native controls where possible. Start in light mode. Show explicit amounts and currencies with locale-aware formatting; preserve minor-unit precision. Keep states and next actions clear. Include default, focus, disabled, loading, empty, error and completed states only where relevant. Payment confirmation must display recipient, amount, currency, fees and timing before submission. A submission acknowledgement is not settlement. Errors must not claim funds are safe or unmoved without authoritative data. Use one Lucide family for UI icons. Label financial statuses in text. Keep accessible names, keyboard paths, reduced motion, large text and RTL layout in scope. Do not mirror the brand identity or reverse numeric strings when adapting RTL. Deliver the smallest usable flow, referenced tokens and key-state fixtures. Identify whether each native example is a concept, source example or tested runtime implementation. Never report a device simulator or web mockup as a physical-device test. --- # Image generation — Omninal ## Current direction — Enterprise 01 One account. Global business. Read `/agent/enterprise-visuals.en.md` or `/agent/enterprise-visuals.zh.md` first, then `/agent/enterprise-prompts.json`. Current masters and bilingual layouts: `/enterprise-visuals/catalog.json`. These standards supersede conflicting legacy guidance below. The six objectives are workspace, terminal, merchant counter, receipt, global operations and account architecture. Use the live account component at `/en/motion#account-motion` or `/zh/motion#account-motion` as the functional reference; generated device screens are illustrative studies, not implementation specifications. Preserve the original SVG logo and #155DFC. 3D explains account relationships, not speculative wealth. Before generation, state the business audience, one communication objective, the account/transaction, exact units and states, scene, framing and delivery language. Compose the original logo and localized headline as separate editable layers. Check financial units, physical devices and every final crop. ## Archived direction — reference only Light mode only for these campaign concepts. Bright neutral daylight, white or near-white backgrounds, natural material detail, refined silver/black devices and restrained brand blue #155DFC. Calm editorial composition, physically credible perspective and room for final copy. No neon, crypto coins, speculative trading imagery, fake certificates or invented partner logos. ## Archived prompt template Create a premium daylight editorial device photograph for an Omninal brand concept. Scene: [specific setting]. Devices: [one to three devices, consistent perspective]. The device UI should be minimal and light, using blue accents, clear white surfaces and neutral financial layout placeholders. Reserve [left/right/top] whitespace for editable brand typography. If a reference photo is supplied, preserve recognizable architecture and lighting; integrate devices naturally without claiming an actual office or event. Do not generate the Omninal logo, partner logos, readable balances, marketing claims, slogans or bank seals. No heavy glow, floating coins or sci-fi holograms. Composition: [ratio]. Output background artwork only. ## Finishing Place the supplied original SVG logo and approved copy afterwards in editable vector layers. Replace every readable device value with approved or explicitly illustrative UI. Check device anatomy, reflections, perspective, logo clear space, copy contrast and safe crop at the final channel size. One aperture motif maximum; it is not required when photography already carries the composition. Never extract or regenerate the central star. ## Historical references — do not use as current defaults ### Merchant and global campaign series Read `/agent/campaign-guide.md` and `/agent/campaign-prompts.json` for the eight merchant/POS and USDC/USDT cross-border concepts. This series permits the short, explicitly illustrative device balances defined in its prompts; it is a deliberate exception to the placeholder-only template above. Original artwork, editable logo/headline SVG layers and 24 finished PNGs are indexed at `/agent/campaigns.json`. Do not imply guaranteed transfer timing, investment returns or actual merchant endorsements. Refinement prompts are supplied at `/agent/campaign-edits.json`. The device gallery includes AI composites using New York photographs by Hannes Richter and Mauricio Chávez. Source and derivative records are supplied in the device catalog and archive. Do not label them as photos of Omninal premises. Reuse original references only under their accompanying usage terms.