NSync
The NxSync Brand System

One brand,
five documents, one truth.

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.

The library

Five documents, clear jobs

Each owns a layer of the brand. They link below — the buttons resolve when all files sit in the same folder.

01 · WHY

Brand Rationale

Intent & meaning

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 Rationale
02 · BRAND

Brand Guidelines v2 SOURCE OF TRUTH

Identity · voice · trust

The canonical book: strategy, ICP, architecture, voice, color, type, AI-trust, enterprise/security, accessibility, i18n, governance. When two documents disagree, this one wins.

Open Guidelines v2
03 · PRODUCT

ERP Product Design System v1.1

Components & behaviour

The 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 System
04 · ASSETS

Logo System & Kit

Marks & files

Production 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 System
05 · COMPONENTS

Component Design System

Interface Elements

The 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 System
How they fit

The source-of-truth order

Brand decisions flow down. Implementation detail flows up to meet them. Tokens are defined once in the Guidelines and shared — no document silently forks them.

01RationaleWhy it exists
02Guidelines v2Brand & voice rules
03Design System v1.1Components & tokens
04Logo KitAsset files
The rule of precedence: for meaning, the Rationale wins; for brand expression, naming, color meaning, voice and tone, Guidelines v2 wins; for how a component looks and behaves in code, the Design System wins; for the actual logo files, the Kit wins.
Quick reference

The essentials, at a glance

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.

Logo construction & usage

mark · clear space · sizing · misuse · motion
  • Grid — viewBox 0 0 64 64. Heavy stroke 9 from (18,48)→(46,16); light stroke 6.2 from (22,16)→(42,48); round caps.
  • Node — 11×11, radius 3.4, centered at the crossing. Pulse only.
  • Forward lean — ~7°, reading as momentum ("next"); never straighten.
  • Clear space — one node-width on every side.
  • Minimum size — 90px lockup / 20px mark. Below 20px use the simplified even-weight mark (no node).
  • Misuse — no equalized weights, recolored/moved node, rotation, stretch, shadow, or gradient.
  • Motion — animate only as a working/sync signal (node beats, strokes rock). Never decorative.

Type scale

Lexend · Inter · JetBrains Mono
Display 700Display
H1 600 · 30/-.03emHeading one
H3 600 · 20/-.02emHeading three
Body 450 · 15/1.65Body copy & UI
Data · JetBrains₹12,45,000.00
Caption · 12/.05emCaption label

Audience

buyers · users
MC
Maya · CFO (buyer)
Accuracy, auditability, close speed, control over AI in finance.
DR
Devon · COO / Founder (buyer)
One system, real-time view, fast time-to-value.
PS
Priya · IT / Admin (gatekeeper)
Permissions, roles, audit, tenant isolation, scoped agents.
TO
Tomas · Finance clerk (daily user)
Fast entry, fewer errors, less reconciliation drudgery.

Iconography & sync motif

1.8px stroke · 24px grid · round

Geometric, calm, never filled. The × motif recurs as a quiet accent — one motif moment per surface; status never relies on color alone.

node-as-connector · divider · empty-state art

Layout & grid

12-col · 24px gutter · 8px base

12 columns, 24px gutters, generous margins. Master-detail and sticky action bars for dense screens.

Spacing scale · 4 / 8 / 12 / 16 / 24 / 32

In application

app icon · signature · social
app icon
Maya Chen
Controller · NxSync
NSync
email signature
NSync
EVERYTHING IN SYNC
social cover
Consistency check

Alignment status

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.

Concern raisedResolutionWhereStatus
No source-of-truth hierarchyDocument precedence definedGuidelines v2 · this indexRESOLVED
AI accountability too lightFull AI-trust framework + patternsGuidelines v2 §AI Trust · v1.1RESOLVED
ERP seriousness not lockedLifecycle/status rules; financial grid & formsDesign System v1.1RESOLVED
"Reversible" vs "permanently removed"Reversibility & deletion policyGuidelines v2 §ReversibilityRESOLVED
Voice needs more copy examplesERP microcopy library + AI voiceGuidelines v2 §MicrocopyRESOLVED
Decorative motion (FAB hover spin)Rule set; needs the actual component editedDesign System v1.0 componentCODE TOUCH-UP
Iris-as-text / Pulse-as-text contrastA11y matrix sets the rule; a few usages to swapDesign System v1.0 componentCODE TOUCH-UP
The honest bit: a document can set a rule, but it can't make a button stop spinning. Three concerns — the FAB hover animation, the couple of places Iris is used as small text on dark, and the "permanently removed" string on a financial record — are rules now, code later. They live in the Design System v1.0 component file, and applying them is a short, well-scoped reconciliation pass rather than a redesign. Everything else is resolved at the document level.