Sixfold OSSixfold OS
01 · Design truth

HexaGrid

HexaGrid keeps design-system logic, component anatomy, accessibility notes, and Figma-linked truth organized in one governed surface.

Dependency graph

How this module connects.

The truth it consumes, the evidence it emits, and where that evidence flows next — hover or focus any node to trace an edge.

CONSUMESDESIGNFEEDSHexaGridDESIGNNormGOVERNANCECoreCODEQenceDOCS
Owns
Design logic, component rules, accessibility notes
Emits signal
design.component.viewed
Governed collections
designLibrariesdesignComponentsdesignVariantsdesignAnatomiesdesignUsageRules
  1. 01Sync Figma truth
  2. 02Review component structure
  3. 03Capture a11y guidance
  4. 04Prepare publish snapshots
System view · Cross-surface

Consistent on every surface.

HexaGrid governs the tokens and components that stay identical across web, mobile, and email.

Surface coverage
TokensGlobal colors
Spacing scale
–
Sizing scale
–
Icon library
–
–
ComponentsButton
–
Input
–
Navigation
–
–
–
App bar
–
–
Grid
–
Card
–
PatternsLogin
–
Registration
–
MFA verification
–
Search
–
Tooltip guidance
–
ArchetypesOnboarding
–
Landing page
Checkout
–
Privacy pages
Abstract

Design truth, version-controlled — before a single line of code depends on it.

HexaGrid is the system of record for design intent. It models components, variants, anatomy, and accessibility contracts as governed, versioned entities — turning a design system from a gallery of screenshots into a queryable, auditable specification that downstream implementation and documentation can bind to.

Module
01 · Design truth
Domain
hexagrid.sixfoldux.com
Owns
5+ governed collections
Signals
3 evidence events
The problem
Design systems decay into folklore.
Without a source of truth, component rules live in Figma comments, Slack threads, and senior designers' heads. Intent drifts silently, accessibility guidance is lost, and every team re-derives the same decisions. HexaGrid makes design intent explicit, versioned, and enforceable.
Mechanism

How it works.

The operating principle, step by step — not a feature list.

  1. 01
    Ingest from Figma
    Sync jobs pull libraries, components, and variants on publish, normalizing them into structured records with stable identifiers.
  2. 02
    Model the anatomy
    Each component carries its anatomy, usage rules, and accessibility notes as first-class fields — not free-text — so they can be validated and referenced.
  3. 03
    Version the contract
    Every change is a versioned delta with provenance, so implementation and docs can pin to a known-good design contract.
  4. 04
    Expose for binding
    Downstream modules resolve a component's current truth by id, closing the gap between what was designed and what ships.
Governed data model

What it owns — and the evidence it emits.

The collections this module governs as source of truth, and the signals it streams downstream into telemetry and governance.

designLibrariesTop-level design system namespaces and their publish state.
designComponentsCanonical components with stable ids that implementation binds to.
designVariantsEnumerated variant matrices — the combinatorial surface of each component.
designUsageRulesMachine-checkable do/don't rules governing correct application.
designAccessibilityNotesPer-component a11y contracts (roles, focus order, contrast intent).
Instrumentation · the evidence it emits
figma.sync.completedA design publish has been ingested and normalized into governed truth.
design.component.viewedDemand signal — which components teams actually reach for.
design.rule.acceptedA usage rule was acknowledged, feeding governance acceptance evidence.
Connections & impact

How it connects — and what measurably changes.

The module consumes upstream truth, emits downstream evidence, moves real numbers, and holds a set of invariants while it does.

Interfaces
Figma
Design libraries and publishes flow in as the upstream source.
HexaCore
Implementation binds components to their versioned design contract.
HexaQence
Documentation anchors reference design entities by id.
Outcomes · what measurably changes
Design–code drift
Falls toward zero as implementation binds to versioned components instead of stale screenshots.
Accessibility coverage
Becomes measurable — every component carries an explicit a11y contract.
Decision reuse
Rises as teams resolve existing truth instead of re-deriving it.
Guarantees · the invariants it holds
  • Every component has a stable identifier and a versioned history.
  • Accessibility guidance is structured data, not a comment.
  • Design intent is resolvable by machines, not just readable by humans.
Resources

Keep exploring.

Framework and resources to go deeper before you commit.

Whitepaper

Framework whitepaper

A public-facing explanation of the Sixfold operating model and why design, docs, AI, insight, and governance should work as one system.

Explore resource
Playbooks

Design-to-governance playbooks

Operational patterns that connect design libraries, implementation releases, telemetry, and review gates.

Explore resource
Glossary

Glossary and terminology

A public terminology entry point that prepares for the deeper HexaQence knowledge surface.

Explore resource

Start with HexaGrid.

Start here when your design system is the thing quietly costing you velocity — HexaGrid turns it into infrastructure.