Detailed Brand Guideline V2 | BLV x Age for AI x ChipOS x Nessha

1. Brand Architecture (Non-negotiable)

Model: endorsed house of brands.

BLV: parent authority and commercial delivery.
Age for AI: education and trust engine.
ChipOS: private enterprise operating layer.
Nessha: operator-facing workspace experience.

Rule: each page maps to one primary brand role. Never combine two separate value propositions in one hero.

Brand	Primary Job	Buyer Intent	KPI
BLV	Implementation + advisory	Can you deliver this for my company?	Qualified consultations
Age for AI	Education + trust	Help me understand AI safely	Engagement + lead capture
ChipOS	Infrastructure proof	Can this run privately and securely?	Technical discovery calls
Nessha	Daily UX proof	Can my team use this every day?	Demo requests

2. Positioning & Messaging

Master sentence: We help founders and SMEs move from AI anxiety to controlled, measurable execution.

Proof pillars

Human-first education
Governance-first execution
Private deployment capability
Practical implementation support

Claim boundaries

Allowed: governed execution, private workspace, policy-based approvals, compliance-aware architecture.

Not allowed: legal certification claims, guaranteed compliance claims, magical AGI claims.

3. Audience & Message Ladder

Primary audience

SME owners and founders
Non-technical operators
Teams afraid of being left behind by AI

Message ladder

AI disruption is real.
Chaos is optional.
Capability is trainable.
Governance is required.
BLV implements the operating model.

4. Logo Rules

Required deliverables: horizontal lockup, stacked lockup, symbol-only mark, favicon, social avatar crop.

Clear space: minimum x around mark (x = cap-height of B in BLV wordmark).
Minimum digital size: horizontal 120px, symbol 24px.
Minimum print size: horizontal 28mm.

Incorrect usage

Do not stretch or rotate logo.
Do not apply shadows/glows.
Do not recolor outside approved palette.
Do not place on low-contrast backgrounds.

5. Color System (Detailed)

BLV Gold
#A89146

BLV Charcoal
#161616

AI Blue
#2F8DE8

AI Violet
#CB3FD2

Warm Sand
#F7F5EF

Paper
#FFFDFA

Deep Ink
#0F172A

Trust Gradient
Blue → Violet

Usage ratio

Neutral backgrounds: 65%
Text neutrals: 20%
Brand accents: 10%
Status colors: 5%

Accessibility baseline

Body text minimum contrast: 4.5:1
Buttons must pass AA
Never use color as sole status signal

6. Typography

Families: Lusitana for headings, Lato for body, Manrope for product UI.

Token	Desktop	Mobile	Use
H1	48/56	34/40	Page title
H2	34/42	28/34	Section title
H3	24/30	20/26	Subsection
Body	18/30	16/28	Main copy
Small	14/22	13/20	Meta/help text

Readability: 70-80 character line length, left-aligned long form, one idea per paragraph.

7. Layout & Components

Breakpoints

Mobile: 0-767
Tablet: 768-1023
Desktop: 1024-1439
Wide: 1440+

Spacing scale

4, 8, 12, 16, 24, 32, 48, 64, 80, 96, 120.

Buttons

Min height 44px
Primary: gradient + white text
Secondary: white + ink border
Ghost: text + underline hover

Motion

Fast 180ms, standard 260ms, reveal 420-620ms
Easing: cubic-bezier(0.22, 1, 0.36, 1)
No decorative endless loops in reading sections

8. Voice & Copy Rules

Voice: calm, practical, direct, responsible, human.

Do

Explain outcomes before complexity.
Use concrete examples.
End pages with one clear next action.

Don't

Overuse hype and abstract AI language.
Use legal/certification claims without basis.
Mix multiple tones in one section.

9. SEO/AEO Standards

One page = one dominant intent
Single H1 only
Unique title + description + canonical
Internal links to at least 2 relevant pages
Schema: Organization, WebSite, Article, Service, FAQPage (if true FAQ)

Use answer-first intros and practical FAQ blocks for AI retrieval systems.

10. Conversion System

Primary offers

AI Transition Consultation
Founder AI Build Partner
Private ChipOS Deployment
Governance and workflow implementation

CTA hierarchy

Book consultation
Read practical guide
Explore framework/book

Lead form minimum fields

Name, company, email, team size, main AI challenge.

11. Governance & QA

Change workflow

Request with rationale
Review by brand + product owner
QA: visual, content, technical
Approve, deploy, log in changelog

Pre-publish QA

Token compliance and contrast pass
Message ladder clarity and CTA clarity
Valid metadata/schema and internal links
Mobile pass and no broken assets

12. 30-Day Rollout

Week 1: lock tokens, navigation, homepage narrative
Week 2: build services + founder page
Week 3: build ChipOS + Nessha product pages
Week 4: SEO cluster + consultation funnel optimization

Success metrics: booking rate, qualified leads, time-on-page, scroll depth, lead-to-project conversion.

Internal use only. Compliance-aware implementation guideline, not legal advice.