Use the shared identity when…
- The surface spans multiple business areas or is the company front door.
- The audience is a client or the public and trust is the priority.
- You are unsure — the shared identity is always a safe, correct default.
Brand System · FEAT-006
Domain identity is a semantic overlay on the one Alterspective brand — not a separate brand and never a raw colour palette. The logo, type, and palette stay constant; a domain shifts emphasis, tone, structure, and iconography so a business area feels purpose-built without fragmenting the brand.
The shared Alterspective identity is the default. Reach for a domain identity only when a surface is clearly owned by one business area and genuinely benefits from its cues.
Each domain declares its default audiences. The audience decides how expressive a surface may be and how much evidence it must carry.
Team-facing product surfaces. Optimise for speed, density, and decision-making. Domain cues are welcome; decoration is not.
Surfaces a client sees inside an engagement. Calmer, evidence-led, and unmistakably Alterspective. Domain identity stays subtle.
Marketing and brand-facing surfaces. The most room for expression — but the expression still has a job: recognition and trust.
Surfaces that span several business areas. Lead with the shared identity and use domain cues only to label, never to theme the whole page.
Surface class is a governed dial for how dense and how expressive a domain surface should be.
Information-first tools. Minimal accent, generous data, no flourish. Used where focus and trust matter most (engineering, security).
The default product surface. Clear hierarchy, one confident accent, real iconography. Most domains live here.
Public, high-impact surfaces. More motion, more storytelling — still governed, never generic. Reserved for marketing-grade work.
Every domain carries an outlined icon from the Alterspective set — never a filled glyph, never an emoji in product chrome. The icon reinforces the domain at a glance.
A domain must be identifiable without relying on colour. Every usage needs a visible
label or an accessible icon with an ariaLabel. Colour-only
domain signalling fails accessibility and is rejected by the validator.
Enforced by UX-BRAND-05 · A11Y-001 and validate_domain_usage.
A domain never introduces a new hex value. It maps six semantic roles to approved brand tokens. That keeps every domain inside the palette, contrast-checked, and automatically correct in dark mode.
accent The domain’s primary emphasis colour — buttons, active states, key marks.
accentText Text/icon colour that sits on the accent. Pre-checked for contrast.
surface The domain panel or container background.
surfaceText Body text colour on the domain surface.
border Dividers and outlines within the domain surface.
focus Keyboard focus ring — always visible, always brand.
Raw hex values are forbidden in a domain record. The validator returns RAW_HEX_ALIAS
for anything that is not a #/palette/* or #/semantic/* reference.
The governed registry below is the single source of truth — the same data that drives the rendered examples, the MCP tools, and the validator.
Workflow, progress, risk, validation, and client delivery execution.
Cue: Marine-led workflow cues with progress, risk, and validation language.
Guardrail: Must not become generic project-management chrome.
Opportunity movement, relationship context, next action, and commercial confidence.
Cue: Marine and Green with opportunity and next-action language.
Guardrail: Must avoid hype or sales-dashboard fakery.
Public signal, campaign readiness, content quality, and brand expression.
Cue: More expressive Chronicle, pattern, and restrained Citrus accent use.
Guardrail: Must not invent off-brand campaign palettes.
Build, deploy, integration health, diagnostics, and technical operations.
Cue: Dense, restrained build and deploy cues with fast functional motion.
Guardrail: Must not look like raw developer tooling by default.
Team health, capability, onboarding, belonging, and sustainable ways of working.
Cue: Green and Marine with warmer copy and sustain/lightbulb cues.
Guardrail: Must keep clear direct Alterspective voice.
Threat posture, controls, access, incident response, and trust operations.
Cue: Navy and Marine with high-contrast status and outlined shield-style cues.
Guardrail: Must not rely on colour-only severity.
Shared operating views, portfolio context, status, and role-led navigation.
Cue: Neutral shell where role, status, and task semantics dominate.
Guardrail: Must not create decorative domain colour shifts.
No results found
Try different keywords or check spelling
Searching...
Start typing to search the documentation