Identity · Section 04
Colour system
Core, interaction, workstream and status colours, including the decision tree and document recipes.
Four layers
Colour is assigned by function, not industry sector. Core colours unify the system; other families answer a specific communication need.
01 · core
Recognition. Covers, mastheads, backgrounds, headings, rules, master diagrams, contractual pages, default tables, neutral charts.
02 · accent
Interaction and technology. Links, calls to action, focus and selection, key technical emphasis, ready status when paired with a word and glyph.
03 · workstream
Optional navigation. Answers which part of the engagement a reader is in — never what colour the whole document is.
04 · status
State only. Always paired with a glyph and a written label.
Decision tree
Ask what the colour is doing before selecting a family.
Is the colour expressing the vcubed brand?
Sapphire, Parchment or Nocturne.
Is it helping a reader navigate a workstream?
Imperial, Verdant or Orchid, locally.
Is it communicating state?
Aqua, Amber, Rowan or neutral — with a glyph and a label.
Is it an interactive action?
Aqua.
None of these?
Do not add colour.
Workstreams
These colours are optional, local navigation signals. They never permanently colour an entire client, sector or document type.
AI implementation
Model selection, evaluation, retrieval, production rollout, model governance.
Platforms, data and integration
Custom enterprise platforms, integrations, data products, architecture.
Adoption, operating model and change
Enablement, product adoption, process design, organisational change.
Status
State is always communicated with colour, a glyph and a written label.
Raw ramps
Use semantic tokens first. Raw ramps are available for data graphics and implementation cases not covered by a semantic role.