The home page for everything NxSync. Start here, then open the document you need — the rationale for the why, the guidelines for the brand, the design system for the product, the kit for the files.
Each owns a layer of the brand. They link below — the buttons resolve when all files sit in the same folder.
The story and the science behind the name, the multiplier mark, the node, and the color — written to convince investors and clients. Read it to understand why every choice was made.
Open Brand RationaleThe canonical book: strategy, ICP, architecture, voice, color, type, AI-trust, enterprise/security, accessibility, i18n, governance. When two documents disagree, this one wins.
Open Guidelines v2The behaviour layer: financial data grid, AI-trust patterns, approvals, document lifecycle, admin & permissions, module blueprints, tokens and developer handoff. Build the product from here.
Open Product Design SystemProduction logo files — wordmark, the × mark, favicon, app icon, mono/one-color, the animated heartbeat, and social images, on-dark and on-light. The kit owns the files; the rules live in §Logo below.
Open Logo SystemThe complete interactive component library — buttons, inputs, tables, cards, alerts, navigation, feedback, advanced patterns, command bar, and agent activity. Use it to keep every screen, state, variant, and motion in sync.
Open Component SystemBrand decisions flow down. Implementation detail flows up to meet them. Tokens are defined once in the Guidelines and shared — no document silently forks them.
The most-reached-for specs in one place — the precise detail the Guidelines summarize, kept here so a designer or developer never has to hunt. For the full narrative, follow each to its document.
Geometric, calm, never filled. The × motif recurs as a quiet accent — one motif moment per surface; status never relies on color alone.
12 columns, 24px gutters, generous margins. Master-detail and sticky action bars for dense screens.
An honest read on the concerns raised in the cross-document alignment review — what's resolved, where, and the one item that needs a practical code touch-up rather than a document.