Colophon.

Design system

v1.1 — Institutional Dark + Champagne. The parent corporate site sits above four product surfaces (arthurgrid.ai, chirongrid.ai, justinegrid.ai, theogrid.ai). The products are light editorial working-surfaces; this site is the dark institutional register that frames them. Champagne (#d6be8e) is the single house accent. Per-product colors appear only inside product cards, never as page-level chrome.

Surfaces step in three: Obsidian #0b0c0f for the page, Graphite #14161b for cards, Ink #1b1e25 for modals. Type sits on three named values: Parchment #f2efe7 (never pure white), Ash #a8aab0, Smoke #8a8d94. Hairlines are translucent white at 6% / 12% + a champagne variant at 30% for accent rules.

Typography

Display + Body: IBM Plex Sans, by Mike Abbink at IBM — humanist sans, slightly carved terminals, distinct numerals. Display headlines run at weight 300 with letter-spacing −0.025em to −0.035em; body is 300/400 at line-height 1.6–1.7; product wordmarks lift to 600.

Mono: IBM Plex Mono, same family. Used for dispatch markers, eyebrows, version stamps, and the tri-region clock chip — anywhere the register turns technical.

Both faces ship via next/font/google: self-hosted at build time, no Google Fonts CDN dependency at runtime, automatic font-display: swap and size-adjust to minimize CLS. The legacy v0.2.0 typography (Outfit + Inter + JetBrains Mono) was retired in v1.1 when the parent-vs-product positioning clarified; the /lab/ specimen routes preserve the exploration as a record.

Stack

Framework: Next.js 15 (App Router, static export). React 19, TypeScript with strict configuration.

Styling: Tailwind CSS 4.1 with design tokens declared in @theme. Legacy v1.0 token names (substrate-N, chrome-N, signal-N) are kept as aliases so detail components don't need to be rewritten on each palette evolution.

3D: Three.js + React Three Fiber + Drei. Two scenes ship — the ambient compositional fabric on every route, and the interactive four-layer architecture diagram on /architecture. Both respect prefers-reduced-motion.

Primitives: Radix UI for dialog and menu components; cmdk for the global command palette.

Infrastructure

Hosted entirely on Microsoft Azure (branded internally as Eve-Grid™). Azure Static Web Apps Standard for the build artifact, Azure Front Door Premium + WAF for the edge, Azure Functions for the API surface (/api/contact sends through Azure Communication Services from donotreply@comms.mindhyve.ai), Azure Key Vault for secrets, Azure Monitor + Application Insights for observability. Provisioned via Bicep.

DNS topology: the apex mindhyve.ai is canonical; www.mindhyve.ai 301-redirects via an AFD rule; mindhyve.io and www.mindhyve.io 301-redirect from a separate Front Door redirector profile. preview.mindhyve.ai stays online as the staging surface, served by the same SWA build behind the same AFD endpoint.

Analytics

Microsoft Clarity for first-party behavioral analytics — session recordings, heatmaps, dead-click and rage-click signals. Cross-Microsoft advertising identity sync (ad_storage) is denied by default; analytics-only consent (analytics_storage) runs full-feature.

Every input on the contact form carries data-clarity-mask so session replays redact name, email, organization, and message body before the bytes leave the visitor's browser. Server-side Application Insights covers the API surface and pipeline runs.

Discipline

Three guardrails ship as build gates and pre-commit hooks.

canon-check — fails any commit or build that introduces vocabulary the Knowledge Brief explicitly retires:

• AGI — superseded positioning; use “Agentic AI”
• Ava-* — legally surrendered trademark prefix; use Eve-*
• HYVE-Grid / HYVE-Fusion — pre-Eve legacy infrastructure names; use Eve-Grid™ / Eve-Fusion™
• “chatbot” / “LLM” / “AI assistant” as a description of MindHYVE products — wrong category; we ship Operating Systems and Digital Employees

Canon authority descends from the MindHYVE Knowledge Brief and the Technical Reference, both internal-classification.

lint-staged + husky — every staged commit auto-runs ESLint (--fix) and Prettier on TypeScript/TSX/JSON/MDX before the message editor opens. CI catches anything the local hook misses.

Lighthouse CI + axe-core — every deploy runs both against the top routes. Hard-fail thresholds: Performance ≥ 0.85, Accessibility ≥ 0.95, Best Practices ≥ 0.9, SEO ≥ 0.6. Three audits are skipped intentionally (uses-http2, third-party-cookies, errors-in-console, inspector-issues) — see the Lighthouse config for the rationale.

This build

v1.0.564 · build local · 2026-06-08T18:02:51.257Z

Authority

Engineered by HYVE Labs, the corporate R&D division of MindHYVE.ai, Inc. Maintained by the Office of the VP of Agentic Operations. Approved by the Founder & CEO. The full release log lives at /changelog.