# NOOS OS Brand Architecture Master File

Version: `V1.0.01`  
Date: `2026-03-28`

## Core Decision

- Masterbrand: `NOOS OS`
- Architecture model: `Branded House` with a controlled sub-brand layer
- Public default language: `Vietnamese`
- Parallel language route: `English` at `/en/...`
- Primary tagline: `The operating layer for trusted human coordination.`
- Vietnamese tagline: `Lớp vận hành cho điều phối con người đáng tin cậy.`

## Why This Direction

- `NOOS` alone is compact and premium, but it carries practical brand collision risk.
- `NOOS OS` keeps the strategic weight of `NOOS` while adding a clearer category descriptor.
- A branded-house system lets product, UX, docs, subdomains and investor materials point back to one master identity.

## Masterbrand System

- `NOOS OS` = masterbrand
- `NOOS Home` = dashboard and primary human surface
- `NOOS Node` = identity and resource graph
- `NOOS Match` = matching and allocation layer
- `NOOS Trust` = trust ledger and verification layer
- `NOOS Host` = place and space layer
- `NOOS Mobile` = mobile app surface
- `NOOS Admin` = internal operations and administration
- `NOOS Flow` = orchestration runtime when exposed as a product brand

## Naming Rules

- Every public sub-brand must follow: `NOOS + short functional word`
- The second word must describe a real operating role, not a poetic abstraction
- Avoid long compounds, metaphor-heavy names and decorative suffixes
- Feature names should stay descriptive and subordinate to the product name
- Internal code names must not leak into public UI

## Tone of Voice

- Calm, precise, systems-oriented
- Ambitious without sounding mystical
- Trust-first, not hype-first
- Human coordination, governance and execution are the recurring themes
- Vietnamese copy must use full diacritics everywhere

## Messaging Stack

### Masterbrand line

`NOOS OS`

### Primary promise

`The operating layer for trusted human coordination.`

### Supporting lines

- `Turn what already exists into real value.`
- `Activate people, places, and communities.`

## Domain and Surface Map

- `noos.iai.one` = public brand site and official docs
- `noos.iai.one/en/...` = English mirror routes
- `app.iai.one` = user-facing application surfaces, future `NOOS Mobile` / `NOOS Home`
- `flow.iai.one` = orchestration runtime, future `NOOS Flow`
- `api.noos.iai.one` = reserved API contract and runtime surface

## Product Copy Rules

- Vietnamese is the default public language
- English must exist as a mirrored route, not just a toggle in the same URL
- Metadata, canonical and `hreflang` must be kept in sync with route language
- Browser title format:
  - Homepage: `NOOS OS — ...`
  - Docs hub: `Tài liệu NOOS OS`
  - Detail page: `Section — Tài liệu NOOS OS`

## Do Not Do

- Do not publish new public modules under standalone names outside the `NOOS + function` rule
- Do not use `NOOS` alone as the primary public title when category clarity matters
- Do not mix accented and unaccented Vietnamese in the same surface
- Do not create subdomains before the product role is mapped to the brand architecture

## Operational Checklist Before New Surface Launch

- Masterbrand placement checked
- Sub-brand naming follows rule
- Vietnamese default copy complete and accented
- English mirror route exists
- Metadata and Open Graph match the route
- Domain/subdomain mapped to product role
- Investor, onboarding and docs copy use the same naming system