04
Brand Voice
Advisory OS speaks like a senior partner who's built the thing they're advising on. Not a vendor. Not a coach. A strategic operator.
Direct
Lead with the point, not the preamble. Cut the warm-up paragraphs. If there's a hard truth, say it.
Precise
Name the specific constraint, not the vague category. "Your close cycle bleeds 4 days" not "your operations could improve."
Warm
Authoritative doesn't mean cold. This is someone who's been where you are and built the way out. Empathy without softening.
Systematic
Everything has a framework, a process, a layer. Language reflects methodology — "three-layer architecture," "constraint priority," "assembly line."
07
Semantic Colors
The core palette (sections 01–06) governs outward-facing content — thought leadership, tools, landing pages. Internal delivery documents (master plans, constraint matrices, project trackers) need an extended palette to represent status, ownership, severity, and progression. These colors layer on top of the core palette, never replace it.
Color discipline depends on context. In outward-facing documents (landing pages, tools, thought leadership), colors serve design roles — accent, hover, depth, hierarchy. In internal delivery documents, every color carries one functional meaning. A color represents a status, an owner, or a state — not decoration. Client brand skills define the specific mappings per engagement, but the discipline is universal: if it's a delivery document, every color is data.
Status
Success
Success
#4a7c6f
--success
Solved constraints, implemented recommendations, wins, completed items, deployed status
Warning
Warning
#a08347
--warning
GPS "Changed" marker, presented status, pattern tags (Recurring, Escalating), caution states
Danger
Danger
#8b4049
--danger
GPS "Escalated" marker, critical themes, urgent constraints
Ownership
Action items, deploy chains, and task assignments use ownership badges. Each role gets one color. These are the AOS defaults — client brand skills override these mappings per engagement (e.g., Crulliance maps gold to team lead, copper to client approver, steel blue to advisor).
Gold form-factor rule. Gold serves both decorative and ownership roles in delivery documents. The form factor carries the distinction: ownership always uses badge, dot, or tag shapes. Decoration always uses bars, underlines, or borders. Never use a gold-bordered card or gold-filled panel to indicate ownership.
Advisor
Advisor (Mine)
#b79d64
--owner-advisor
Kathryn's action items, advisor-owned tasks, "Mine" badge
Client
Client
#5a8a9a
--owner-client
Client action items, client-owned tasks, "Client" badge
Team
Team
#8a6a9a
--owner-team
Team member actions (e.g., Pooja-specific tasks), "Team" badge
Surfaces
Internal documents layer panels on top of the charcoal background. These create visual depth without introducing new hues.
Charcoal
#1a1a1a · Background
Deep Charcoal
#2a2a2a · Nested elements
Opacity Variants
Gold at reduced opacity for subtle accents — conversation borders, hover states, background tints.
Gold Dim
rgba(183, 157, 100, 0.3) · --gold-dim
Gold Full
#b79d64 · --gold · Hover / active
Where Each System Applies
| Document Type |
Palette |
Theme |
Color Discipline |
| Thought leadership |
Core only (sections 01–06) |
Dark |
Design roles |
| Micro-tools |
Core only |
Dark |
Design roles |
| Diagnostic micro-tools |
Core + Status (no ownership) |
Dark |
Status colors for scored results |
| Landing pages |
Core only |
Dark |
Design roles |
| Client Master Plan |
Core + Semantic |
Dark |
One color = one meaning |
| Constraint Priority Matrix |
Core + Semantic |
Light (client-branded) |
One color = one meaning |
| Project Plans |
Core + Semantic |
Light (client-branded) |
One color = one meaning |
| SOPs |
Core + Semantic |
Light (client-branded) |
One color = one meaning |
| Blueprints |
Core + Semantic |
Light (client-branded) |
One color = one meaning |
| Cadence / Rapport (apps) |
Core + Semantic |
Dark |
One color = one meaning |