The single
source of truth.
Everything required to build, write, design, sell, and ship NxSync — the AI-native ERP — as one coherent brand. This edition extends the v1.0 identity into the full product-behaviour, AI-trust, enterprise, and handoff system an ERP demands. When two documents disagree, the hierarchy in §0 decides. When in doubt, this document wins.
How to use this · document hierarchy
NxSync's brand lives across several documents. They are not peers. This hierarchy resolves the governance question raised in review — "if the guidelines and the design system disagree, which wins?"
| # | Document | Owns | Wins on conflict about… |
|---|---|---|---|
| 1 | Brand Rationale | Why the brand exists; why choices were made | Intent & meaning |
| 2 | Brand Guidelines (this) | Identity, voice, color, type, messaging, trust principles | Brand expression, naming, tone, color meaning |
| 3 | Design System v1.0 | Components, interaction, UI tokens (implementation) | How a component looks & behaves in code |
| 4 | ERP Product System v1.1 | Workflows, data grid, AI-trust patterns, admin, governance | ERP behaviour & enterprise patterns |
The rule
Brand-level decisions (color meaning, voice, naming, the mark) flow down from this document. Implementation detail (a hover timing, a prop name) is owned by the design system. Tokens are shared and defined once here (§Tokens) — neither doc may silently fork them.This edition's changelog
- Added AI Trust & Agent Behaviour, Enterprise/Security/Compliance, Brand Architecture, Naming system, Reversibility policy, ERP microcopy library, Data-viz & Sound identity, Responsible-AI values, sharpened ICP, full token tables, contrast matrix, i18n.
- Fixed four cross-document drifts flagged in review (see §Drift control): decorative motion, irreversibility language, light AI layer, missing hierarchy.
- Renamed the prior file to Brand Guidelines v1.0 — Identity, Voice & Visual System; this supersedes it.
Purpose & the four pillars
Positioning statement
The four pillars
| Pillar | Means | Shows up as |
|---|---|---|
| Synced | One real-time source of truth | Live status, reconciliation, no stale reports |
| Intelligent | AI that reasons over your data | Suggestions, drafts, insights, the Agent |
| Transparent | Every action explainable & reversible | Source trace, diffs, audit trail, undo |
| Effortless | Power without friction | Command Bar, calm dense UI, sensible defaults |
Archetype: Sage (clarity, judgment, truth) with a measured touch of Magician (transformation). Never the Jester, never the Hero who shouts.
The promise & the trust thesis
In an AI-native ERP, trust is the product. Customers will not let AI touch finance, payroll, inventory, or compliance unless they can inspect it and undo it. Every brand decision is downstream of this.
NxSync reasons, acts, and shows its work. Nothing posts without a trail. Anything it does, you can see, question, and reverse.
"Set it and forget it." We never imply AI runs your books unsupervised, never hide a step, never present certainty we don't have.
Responsible-AI values
Neither review asked for it, but an AI-native ERP brand without a stated AI stance is a liability. These are commitments the brand must be able to defend — in a sales call and in a deposition.
| Value | What we commit to |
|---|---|
| Human oversight | Material financial, legal, payroll, and tax actions require human approval by default. Autonomy is granted, scoped, and revocable. |
| Explainability | Every AI action carries its reasoning and source data. "Because the model said so" is never an acceptable answer. |
| Reversibility | AI actions are reversible or correctable. We design for undo before we design for speed. |
| Data ownership | Customer data belongs to the customer. We do not train shared models on customer data without explicit, revocable consent. |
| Bounded autonomy | Agents act only within limits an admin set — amount caps, scopes, environments — and flag everything outside them. |
| Honesty about limits | We show confidence and uncertainty. We escalate rather than guess. We name mistakes plainly. |
ICP & segmentation
"Operations-heavy companies" is the right instinct but too broad to sell against. Sharper segments for marketing and sales:
| Segment | Who | Why now |
|---|---|---|
| Primary ICP | Mid-market firms with finance + inventory + procurement + field ops (50–1,000 staff) | Outgrew spreadsheets & point tools; legacy ERP is too heavy/slow |
| Early adopter | Founder-led businesses past the spreadsheet stage | Want one connected system without an SAP-scale project |
| Beachhead geographies | India, UAE, Saudi, Morocco → broader EMEA/APAC | Multi-currency, multi-tax, multi-entity from day one |
Buyers, users & pains
| Role | Type | Cares most about |
|---|---|---|
| CFO | Buyer | Accuracy, auditability, close speed, control over AI in finance |
| COO / Founder | Buyer | One system, real-time view, less manual ops, fast time-to-value |
| IT / Admin | Buyer / gatekeeper | Permissions, roles, audit, tenant isolation, scoped agents, security |
| Finance clerk | Daily user | Fast entry, fewer errors, less reconciliation drudgery |
| Ops / warehouse manager | Daily user | Live stock, reorder alerts, simple approvals on mobile |
Top pains we relieve
- Delayed, stale reporting and month-end fire drills.
- Manual reconciliation and data re-keying between tools.
- Approval bottlenecks and lost paper trails.
- Disconnected tools that disagree with each other.
Competitive contrast
| Alternative | Their gravity | NxSync contrast |
|---|---|---|
| Spreadsheets / point tools | Flexible, cheap, familiar | Connected & live — no re-keying, one source of truth |
| Tally / Zoho / Odoo | Affordable, broad | AI-native action + reversibility + real-time sync, not bolted-on |
| NetSuite / SAP-class | Powerful, enterprise-trusted | Modern, calm, fast to adopt; AI you can audit & undo |
| Custom builds | Tailored | Maintained, secure, multi-entity, no in-house upkeep |
Brand architecture
As the website, ERP, automation engine, control plane, docs, and customer portal multiply, the brand needs one clear model. Recommended: a branded house — one customer-facing product brand, technology tiers kept internal.
| Entity | Role | Surfaces as |
|---|---|---|
| Synchronos | Parent company | "NxSync, by Synchronos" — corporate, careers, legal, investor |
| NxSync | The product (master brand customers know) | Product, marketing, app, docs, support |
| AutoCore | Automation/agent engine that powers NxSync | Ingredient/tech tier: "powered by AutoCore" in technical & partner contexts only — never competes with NxSync for attention |
| Control plane / ERP Core | Backend infrastructure | Never in product UI or marketing |
⚠ Confirm before publishing
The relationships among Synchronos.tech, Synchronos Solutions, AutoCore, and the ERP Core/control-plane references are inferred. This is the recommended architecture; validate the legal/product reality and lock it before external use.Naming system
A canonical vocabulary so features, actions, records, and states are never invented ad-hoc. Use these exact words in product, docs, and marketing.
| Category | Canonical terms |
|---|---|
| Modules | Finance · Sales · Purchase · Inventory · HR · Payroll · Projects · CRM · Reports · Admin |
| AI features | Agent (acts) · Ask (Command-Bar Q&A) · Automations (rules/workflows) · Suggestions · Insights |
| Actions | Post · Approve · Reconcile · Sync · Reverse · Void · Archive · Assign · Close · Reopen · Submit · Recall |
| Records | Invoice · Bill · Journal entry · Payment · Purchase order · Goods receipt · Shipment · Quote · Sales order |
| Statuses | Draft · Submitted · Pending review · Approved · Posted · Reversed · Voided · Failed · Synced · Needs review |
| Agent states | Suggested · Waiting approval · Running · Completed · Needs review · Blocked |
Say Agent and Ask. Keep one verb per concept (always "Post", never "Submit to ledger").
Avoid Copilot (owned connotation) and generic Assistant/Bot. No synonyms drift ("undo" vs "reverse" vs "rollback" → pick Reverse for posted records).
The Agent persona
The Agent is the brand's most sensitive surface — it speaks while touching money. It needs a defined personality and a first-person rule, which neither review specified.
| Trait | Definition |
|---|---|
| Name | "the NxSync Agent" — a capability, not a mascot. No cute human name (over-anthropomorphizing AI that moves money erodes trust). |
| Person | First person only when proposing/explaining its own work: "I matched 142 of 148." Product chrome stays second-person/imperative: "Post entry." |
| Personality | A precise, candid analyst. Confident about evidence, honest about uncertainty, never chatty, never apologetic-cute. |
| Never | Claims feelings, hides a step, uses "I" to dodge accountability, or implies it acted without permission. |
Voice & tone
We write from the user's side of the table. Plain verbs, sentence case, no hype. Calm under pressure — most reading happens during a problem.
| Context | Tone | Example |
|---|---|---|
| Routine | Quiet, factual | Entry posted. |
| AI proposing | Helpful, sourced | I found 4 likely duplicates. Review? |
| Risk / money | Direct, serious | This releases $44,300. Confirm to continue. |
| Error | Honest, no blame, next step | Sync stopped at 142 of 148. 6 need a fix. |
| Empty | Inviting, points forward | No purchase orders yet. Create one or import a CSV. |
Messaging hierarchy
| Tagline | Everything in sync. |
| One-liner | The AI-native ERP that reasons, acts, and shows its work. |
| Elevator | NxSync keeps your whole business on one live source of truth and lets AI do the reconciling, drafting, and matching — transparently and reversibly, so you stay in control. |
| Boilerplate | NxSync is an AI-native ERP for growing, operations-heavy companies. It unifies finance, sales, purchase, inventory, and HR in real time, and lets AI act on your behalf with full auditability and one-click reversal. |
Vocabulary & mechanics
sync, in sync, source of truth, post, reconcile, reverse, review, approve, on the record, the Agent, Ask, real time.
magic, effortless-AI, seamless, revolutionary, blazing-fast, set-and-forget, "just trust us", and any verb that hides a step.
| Mechanic | Rule |
|---|---|
| Headings & UI | Sentence case. Buttons are verbs: Post, Approve. |
| Numbers / money | Tabular figures (JetBrains Mono); locale-formatted (see i18n). Always show currency. |
| Dates | 13 Jun 2026 — unambiguous, never 06/13/26. |
| Errors | State what happened + the next step. Never apologize twice, never blame the user. |
AI voice
How the Agent speaks — the exact phrasings that keep AI trustworthy in a ledger.
ERP microcopy library
The moments that matter more than any tagline. Canonical strings for the states an ERP hits daily.
| Moment | Copy |
|---|---|
| Permission denied | You don't have access to post entries. Ask an approver, or request access. |
| AI needs approval | The Agent prepared this. It posts after your approval. |
| Partial sync | Synced 142 of 148. 6 transactions need a fix. |
| Integration failed | The bank connection expired. Reconnect to resume syncing. |
| Duplicate found | This looks like INV-2840, posted yesterday. Post anyway, or open the original? |
| Closed period | June is closed. Post to an open period, or ask an admin to reopen June. |
| Reversal requested | Reversal created. The original entry stays on the record, marked reversed. |
| Low confidence | Low confidence (34%) — source data is incomplete. Review before posting. |
| Missing source doc | No source document attached. Add one, or post without (logged). |
| Reconciliation mismatch | This doesn't match the bank line by $42. Adjust, or flag for review. |
| Tax rule conflict | Two tax rules apply here. Choose one to continue. |
| Export complete | Export ready — 1,204 rows. Download, or it's in your files. |
| Bulk action warning | This approves 38 invoices ($412,000). Review the list before you confirm. |
| Irreversible action | This permanently deletes the integration and its logs. It can't be reversed. Type DELETE to confirm. |
Logo & mark
The mark is the multiplier × — two crossing streams held by a single Pulse node at the center: many functions, one live source of truth. It doubles as the lowercase x in the wordmark.
| Rule | Spec |
|---|---|
| Stroke weights | Uneven by design (heavy 9 / light 6.2). Never equalize. |
| The node | Pulse only, at the crossing. Never recolor or move it. |
| Small sizes | Below 20px use the simplified mark (even weight, no node). |
| Motion | Animate only as a working/sync signal (node beats, strokes rock). Never decorative. |
| Misuse | No shadows, gradients on the mark, rotation, stretching, or off-brand colors. |
Full variants (mono, one-color, app icon, favicon, animated, social) live in the Logo Kit. This document owns the rules; the kit owns the files.
Color
Color is meaning, never decoration. The neutral ramp does the heavy lifting; Iris carries intelligence and action; Pulse signals what's live.
Semantic (finance) — never recolored for branding
The 80/15/5 discipline is what makes Pulse mean "live."
Color tokens · light / dark
| Token | Purpose | Dark | Light |
|---|---|---|---|
| color.action | Primary actions, focus, links | #6A5CFF | #5A4FE8 |
| color.action.text | Accent text on bg (a11y-safe) | #9389FF | #4A3FD8 |
| color.live | AI / synced state | #2EE6C5 | #13B89C |
| color.bg | App canvas | #0A0C16 | #F7F8FC |
| color.surface.1 / 2 / 3 | Cards, panels, raised | #11131F / 171A28 / 1E2233 | #FFFFFF / F3F4FA / ECEEF6 |
| color.text.1 / 2 / 3 | Primary / secondary / tertiary | #ECEDF4 / A6AAC2 / 6E7289 | #13151F / 535873 / 8C90A6 |
| color.border / border.2 | Lines / strong lines | #262A3B / 343A54 | #E4E7F1 / D2D6E6 |
| color.pos / neg / warn | Credit / debit / attention | #33C088 / EE5B6A / F6A23B | #1FA774 / D83A4A / D98521 |
| radius.s / m / l | Controls / cards / sheets | 8 / 12 / 16px | 8 / 12 / 16px |
| space.1–6 | Spacing scale | 4 / 8 / 12 / 16 / 24 / 32px | same |
| motion.fast / base / slow | Micro / transition / overlay | 140 / 240 / 320ms · ease (.4,0,.2,1) | same |
Note the two Iris tokens: color.action (fills) and color.action.text (accent text) — see the contrast matrix for why.
Typography
| Face | Use | Why |
|---|---|---|
| Lexend | Display, headings | Rounded terminals echo the mark; legible across ages |
| Inter | UI, body | Workhorse clarity at dense sizes |
| JetBrains Mono | IDs, money, code, tabular data | Tabular figures align columns — a low-vision aid too |
Iconography & the sync motif
- Icons: 1.8–2px stroke, round caps/joins, 24px grid, geometric and calm — never filled, never playful.
- The × motif: reuse the crossing/node as a quiet graphic device — section accents, dividers, empty-state art. One motif moment per surface; never competes with content.
- Status is never color-only: every badge carries a label or icon (accessibility + print-safe).
Imagery & illustration
Real product UI on the Void canvas. Candid, in-context operators (not posed stock smiles). Data as texture — charts, ledgers, the sync motif as abstract art.
No glowing-brain/robot-hand AI clichés. No fake dashboards with impossible numbers. No generic "business handshake" stock. No screenshots that misrepresent the product.
AI-generated imagery: allowed for abstract/texture only, never to fabricate product screens, customers, or results. Label where context requires.
Data visualization
ERP is charts. They need their own palette rules so they stay legible, accessible, and on-brand.
| Chart type | Palette rule |
|---|---|
| Single series | Iris. Forecast/secondary in muted Iris or dashed. |
| Positive / negative | Always pos / neg — semantic, never branded. |
| Categorical (≤6) | Iris → Pulse → Ember → neutral steps; distinct in hue and value (color-blind safe). |
| Sequential / heat | One ramp (Iris light→dark). Never rainbow. |
| Labels | Direct-label where possible; tabular-figure tooltips; never rely on color alone for meaning. |
Motion
Motion is meaning. For a calm enterprise ERP it must be restrained — reserved for state change, AI activity, sync, progress, review, success, and risk.
⚠ Drift resolved
The design system's decorative FAB rotate-on-hover contradicts this rule. Decorative hover motion is now disallowed; the design system will be updated so the FAB uses a subtle color/elevation change only. Animate because something happened, not because a cursor passed by.| Allowed | Not allowed |
|---|---|
| Node pulse = AI thinking/acting | Spinning/bouncing on hover |
| Progress, sync, skeleton loading | Parallax, confetti, bounce easing |
| State transitions (post, approve, reverse) | Looping ambient animation |
| Toast/modal enter-exit (240–320ms) | Anything over ~320ms in-app |
Tokens: 140 / 240 / 320ms, ease cubic-bezier(.4,0,.2,1). prefers-reduced-motion always honored.
Sound
- Default silent. An ERP is a workplace; sound is opt-in.
- Two cues only: a soft mid-tone for agent task complete / approval needed, a lower tone for error/needs review. Short, non-melodic, calm.
- Never for routine saves. Always pair with a visual cue (sound is never the only signal — accessibility).
Layout & grid
- Spacing scale: 4 / 8 / 12 / 16 / 24 / 32px. Radii 8 / 12 / 16.
- App shell: left nav + top bar + content + optional right detail pane (master-detail). Sticky action bar for forms.
- Density: comfortable default; a compact mode for power users (data grids). Defined in Design System.
- Responsive: desktop-first; tablet collapses nav to icons; mobile uses bottom nav, cards over tables, bottom-sheet actions, full-screen Command Bar.
Product principles
| Principle | In practice |
|---|---|
| Role-based | The UI shows what your role can act on; denied actions are disabled, not hidden-then-broken. |
| Coherent | One component vocabulary across every module (Design System v1.0). |
| Adaptive | Any device, any theme, any locale — same logic. |
| Calm | Density without noise. Color and motion are rationed. |
| Trustworthy | Every consequential action is explainable, reversible, logged. |
ERP surface map
What each surface must deliver at brand level. Detailed components live in Design System v1.0 / ERP Product System v1.1.
| Surface | Must provide |
|---|---|
| Dashboard | KPI cards, alerts, drilldowns; executive vs operator views |
| Finance | Journal entries, ledgers, reconciliation, period close, audit trail |
| Procurement | Requests, approvals, vendor comparison, PO lifecycle, 3-way match |
| Inventory | Stock movement, reorder alerts, warehouse views, batch/serial |
| HR / payroll | Employee records, approvals, sensitive-data states |
| Admin | Roles, permissions, tenant settings, integrations, environments |
| Reports | Filters, exports, scheduling, explainable (drillable) numbers |
| Agent panel | What it did, why, confidence, source, approval status, rollback |
Document lifecycle & status
One canonical state machine for every financial document — so a badge means the same thing in every module.
Reversibility & deletion policy
The brand promises "reversible," yet the design system shipped "permanently removed · cannot be undone." Both can be true — but only under an explicit policy. Here it is.
| Record type | Correct action | Hard delete? |
|---|---|---|
| Posted financial entry | Reverse (creates a correcting entry; original stays on record) | Never |
| Unposted draft | Discard / delete | Yes (no ledger impact) |
| Invoice / bill in error | Void (kept, marked void) or credit note | Never |
| Master data (vendor, item) | Archive (soft delete; restorable) | Admin only, if unused |
| Audit logs | Immutable | Never |
| Integration / non-financial config | Delete (with typed confirm) | Yes · irreversible warning required |
⚠ Copy rule
"Permanently removed / cannot be undone" is permitted only for genuinely irreversible, non-financial actions (e.g. deleting an integration) and must use the typed-confirm pattern. It must never appear on a financial record — those reverse, void, or archive.Autonomy & approval gates
The most important section for an AI-native ERP. The human always holds the dial.
| Autonomy level | Behaviour | Default for |
|---|---|---|
| Suggest only | Surfaces a suggestion; nothing happens until you act | New teams; sensitive areas |
| Draft | Prepares the entry; never posts it | Finance (recommended default) |
| Approve-first | Executes routine work into an approval queue | High-volume, low-risk |
| Auto-run | Acts within scoped rules/limits, logs everything, flags exceptions | Vetted, bounded tasks only |
Always require human approval — regardless of autonomy level
- Payments & payouts · payroll runs · tax filings.
- Role/permission changes · data export of sensitive records.
- Anything above an admin-set amount limit, or outside an agent's scope.
Confidence, source & audit
| Pattern | Rule |
|---|---|
| Confidence | Show a level (high/med/low + %) whenever the Agent proposes a record change. Low confidence blocks one-click apply. |
| Uncertainty / conflict | Name it: "two invoices match this amount." Offer the choice; never pick silently. |
| Source trace | Link the evidence — invoices, ledger lines, bank lines, emails. "Show your work" is mandatory for any posting. |
| Before/after diff | Show the change before it's applied to a record. |
| AI vs human label | Every record shows who acted: Agent vs person, and who approved. |
| Audit trail logs | Actor, timestamp, source data, model/version, reasoning summary, approver. Immutable. |
| Rollback | Reverse is one action from the executed-action record; reversal window stated ("reversible for 24h"). |
Sensitive actions
Payments, payroll, tax, deletion, role changes, and bulk data export get stepped-up friction — by design.
- Typed confirmation for irreversible or high-value actions ("type RELEASE").
- Amount & recipient restated in the confirm step; audit-promise shown ("logged to the audit trail").
- The Agent may never complete a sensitive action autonomously — it can only prepare it for human release.
Trust, security & control messaging
For CFOs, founders, and IT heads, the brand must communicate control — not just beauty and intelligence. How we talk about it:
| Topic | How we say it |
|---|---|
| Data ownership | "Your data is yours. We don't train shared models on it." |
| Privacy & isolation | "Every tenant is isolated. Access is role-scoped and logged." |
| Access control | "Granular RBAC; agents act only within the scope you grant." |
| Audit | "Every action — human or AI — is on the immutable record." |
| Residency | "Choose where your data lives." (state regions actually offered) |
| Resilience | "Encrypted, backed up, with tested recovery." (state RPO/RTO when available) |
| Deployment | "Cloud, private cloud, or on-prem." (only options actually offered) |
Compliance & claims policy
State certifications only once held ("SOC 2 Type II", "ISO 27001", "GDPR-compliant"). Use "in progress" / "readiness" for pursued-not-held. Date claims.
Never imply a certification you don't hold. No "bank-grade", "military-grade", "100% secure", "unhackable". No legal/financial guarantees the product can't make.
Accessibility — proof
We claim WCAG 2.2 AA. Here is the evidence, with measured contrast ratios. Pairs that fail as text are restricted to fills/icons.
Contrast matrix — dark theme (on #0A0C16)
| Pair | Ratio | Use |
|---|---|---|
| Text-1 #ECEDF4 | 16.7:1 | AAA · body |
| Text-2 #A6AAC2 | 8.5:1 | AAA · secondary |
| Text-3 #6E7289 | 4.11:1 | large / non-essential only |
| Iris-bright #9389FF | 6.74:1 | AA · accent text & links |
| Iris #6A5CFF | 4.26:1 | fills & large only — not body text |
| Pulse #2EE6C5 | 12.29:1 | AAA · live/data text on dark |
| Positive #33C088 | 8.39:1 | AAA |
| Negative #EE5B6A | 5.89:1 | AA |
| White on Iris #6A5CFF | 4.58:1 | AA · button text |
Contrast matrix — light theme (on #FFFFFF)
| Pair | Ratio | Use |
|---|---|---|
| Text-1 #13151F | 18.2:1 | AAA · body |
| Text-2 #535873 | 6.97:1 | AA · secondary |
| Iris #5A4FE8 | 5.65:1 | AA · accent text & buttons |
| Negative #D83A4A | 4.54:1 | AA |
| Pulse-deep #13B89C | 2.51:1 | fills/icons only — never text |
| Positive #1FA774 | 3.07:1 | icons/large — darken for body text |
| Requirement | Rule |
|---|---|
| Focus | Visible 2px Iris ring on every interactive element; never removed. |
| Error states | Color + icon + text; errors announced to screen readers; field association via aria-describedby. |
| Agent activity (SR) | Live region (polite): "Agent matched 142 of 148. 4 need review." |
| Keyboard map | Grid: arrows move, Enter edits, Space selects, Esc cancels · Modal: focus trapped, Esc closes, focus returns · Tabs: ←→/Home/End · Command Bar: ⌘K. |
| Reduced motion | All non-essential animation disabled; node pulse becomes a static dot. |
| Dense grids | Row/col headers associated; sortable state announced; sticky header keeps context. |
| Non-color signal | Status always carries text/icon, never color alone. |
Internationalization
| Locale | Currency | Number | Date | Tax |
|---|---|---|---|---|
| en-IN | ₹ 12,45,000.00 | lakh/crore | 13 Jun 2026 | GST |
| en-US | $ 1,245,000.00 | 1,234.56 | Jun 13, 2026 | Sales tax |
| ar-AE | د.إ 1,245,000.00 | RTL | ١٣ يونيو ٢٠٢٦ | VAT |
| ar-SA | ر.س 1,245,000.00 | RTL | Hijri option | VAT / Zakat |
| fr-MA | 1 245 000,00 MAD | space · comma | 13 juin 2026 | TVA |
- Never concatenate translated strings; reserve +35% width for expansion.
- RTL (Arabic): mirror layout, icons, and progress direction; keep the mark unmirrored.
- Languages: EN, AR, FR, HI as priority; money stored in minor units, formatted per locale for display only.
- Multi-entity: show legal entity, branch, and base currency in the tenant switcher; reports can consolidate across entities.
- Timezones: store UTC, display in the user's zone; show zone on timestamps that cross entities.
Tokens & developer handoff
Brand owns the token meanings (above); engineering owns the export. One source, multiple formats — no forking.
| Deliverable | Form |
|---|---|
| Tokens | CSS custom properties · Tailwind config · JSON (Style Dictionary) |
| Components | Typed React library; props contracts (see ERP Product System v1.1) |
| State matrix | Every component implements: default · hover · focus · active · disabled · loading · error · empty · permission-denied |
| Component rules | Button hierarchy (1 primary/view) · field states · table density · modal vs drawer vs page · toast/skeleton patterns |
| Design source | Figma library mirrors tokens 1:1; design↔code parity is a release gate |
Drift control — resolved
The alignment review flagged where the documents had drifted apart. Each is now resolved and pointed to its governing section.
| Drift flagged | Resolution | Owns it |
|---|---|---|
| Decorative motion (FAB spin) vs "motion is meaning" | Decorative hover motion disallowed; restraint rule set | §Motion |
| "Permanently removed" vs "reversible" promise | Reversibility & deletion policy; copy restricted to non-financial | §Reversibility |
| AI accountability layer too light | Full AI Trust framework added (autonomy, confidence, source, audit, labels, sensitive) | §AI Trust |
| ERP seriousness not locked | Lifecycle & status rules; financial-grade grid/forms in v1.1 | §Lifecycle · v1.1 |
| No source-of-truth hierarchy | Document hierarchy defined | §How to use |
Governance, maintenance & KPIs
| Area | Rule |
|---|---|
| Ownership | Brand & Design Systems team owns this document; domain squads own module specifics within these rules. |
| Maturity | Every component/pattern is draft → beta → stable → deprecated (see v1.1 gates). |
| Change process | Proposals via PR to the system repo; brand-level changes need Brand sign-off; SemVer with migration notes for breaking changes. |
| Asset management | Logos in the Logo Kit; tokens in the design-token repo; this guide is the canonical narrative. No private forks. |
| Test gates (to "stable") | Keyboard + screen-reader pass · AA contrast both themes · all nine states · visual-regression snapshots · docs + Figma parity. |
| Brand KPIs | Aided/unaided recall · "trust" & "control" attribute scores in buyer research · design-system adoption rate · accessibility audit pass rate · time-to-first-value. |
| Exceptions | Anything off-guide is time-boxed, logged, and reviewed; the most legible, calmest, most reversible option wins ties. |
NxSync Brand Guidelines v2.0 · Source of Truth · supersedes v1.0 · companion to Design System v1.0 & ERP Product System v1.1 · Everything in sync.