Keelmesh · Brand and website brief · 2026-10-11

Design a precise, memorable international product for people and AI agents to
operate authorized infrastructure through trusted encrypted device connections.
Keel means the stable backbone; mesh means connected peers. Give the brand an
original K-shaped backbone with converging routes. No animals, shields, padlocks,
atom orbits, skulls, fake quantum hardware, or imitation of existing brand marks.

Website revision: use a warm paper background, charcoal text, deep teal details
and one muted sand illustration surface. Introduce the usable product first:
remote terminals, files and paired devices. Show a compact interface example,
clearly labelled as illustrative, with terminal/file/activity tabs. Use simple
line drawings to explain direct and relayed connections. No orbiting hubs,
animated dotted connections, gradients, glows, sparkle symbols or trust-badge rows.
Use self-hosted Manrope for Latin and native CJK fallbacks. Use the original solid K mark with filled geometric outlines, a continuous keel
and an open channel between the arms. The desktop itself stays compact and retains its current operational layout.

Reference principles: Tailcat's plain explanations and terminal-led product
illustration; Linear's product-led hierarchy and restrained controls; Raycast's
single primary download action. Develop original layouts and assets rather than
copying logos, artwork, text or interface assets from these products.
Sources: https://tailscale.com/tailcat ; https://linear.app ; https://www.raycast.com

Writing: describe what users can do and what they must configure. Prefer short
sentences and concrete nouns. Avoid 'trust-anchored', 'intent to action', 'fabric',
'one foundation, three roles' and other abstract category-building slogans.
Keep AI as an actual optional capability, not the theme of every heading.
Keep engineering previews in a secondary, expandable roadmap section. No repeated
numbered section labels, giant colored heading pairs or interchangeable feature
card grids. Never invent customer logos, testimonials, performance counts or
command results from real devices. Illustrative names and output are fictitious.

Story: AI intent → verified device identity → scoped permission → encrypted device
session → auditable action. Call out that the browser diagram is illustrative.
Show available management/AI tools separately from the VPN engineering preview.
Do not claim a public MCP server, SDK or production VPN unless implemented.
Describe the cryptography as hybrid post-quantum; no absolute security, independent
audit or FIPS certification claims. macOS Beta remains ad-hoc and unnotarized.

International: English default plus complete Simplified Chinese, Japanese, German,
French and Spanish pages. Each page gets correct lang, canonical, reciprocal
hreflang, localized metadata, navigation, examples, FAQ and installation content.
Language selection is explicit. No flags, forced geolocation or auto-redirect.
Switching languages preserves a valid section anchor. Work without JavaScript.
Provide reduced-motion support, semantic headings, visible keyboard focus,
usable tap targets, 200% zoom and no horizontal overflow at 320–1440 px.

Names: Keelmesh (console and product family), Keelmesh Tunnel (VPN preview),
Keelmesh Core (identity/cryptography foundation). Website branding uses Keelmesh; legal operator details remain in the privacy notice.
Deep330 is reserved as the separate communications-series codename.

Compatibility: retain bundle ID com.wails.deepops, executable DeepOps, deepops CLI,
config paths, Keychain services, device identity and cryptographic protocol names.
Rename the visible app to Keelmesh.app. Keep previous release URLs immutable.
Host at https://keelmesh.com/; retain redirects from ant.genesiu.com/deep/.

2026-10-12 logo revision: filled geometric K, no thin decorative strokes.
Keelmesh.com public contact: keelmesh@genesiu.com.
Company operator identity appears only in the privacy notice, without promotional
claims about a group or its geographic reach. No director information or private documents are published.

Product-first presentation: no group-company publisher announcement in the homepage,
footer, roadmap or product/contact page. Keep legal operator identity in privacy.
