# ENTIA Brand Kit

Snapshot for the Design team — 2026-04-29.

Brand: **Entia** (commercial). Legal entity: **PrecisionAI Marketing OÜ** (Tallinn, Estonia).
Primary domain: `entia.systems`. Secondary: `dahe.store`, `mcp.entia.systems`, `api.entia.systems`.

## Structure

```
docs/BRAND_KIT/
├── README.md                  ← this file
├── 01_LOGOS/                  ← all logo PNG/SVG + favicons + USAGE.md
├── 02_TYPOGRAPHY/             ← typography.md (Inter, JetBrains Mono, deprecated faces)
├── 03_COLORS/                 ← colors.md, colors.css (CSS variables), legacy tokens
├── 04_HEADER_FOOTER/          ← glass-header HTML, footer JS, nav JS
├── 05_ICONS/                  ← LLM logos (SVG sprite + CSS), MCP icon
├── 06_LANDING_STYLES/         ← landing.css consolidated, pattern reference
├── 07_GUIDE/                  ← BRANDING_GUIDE.md (tone, identity, do/don't)
├── MISSING.md                 ← assets that do NOT exist in repo (zero-fabrication)
└── 08_DOWNLOAD_BUNDLE.sh      ← creates BRAND_KIT_2026-04-29.zip
```

## Source of truth

All assets in this kit were extracted from the live ENTIA codebase:
- Logos and favicons: `public_html/assets/` and `public_html/`
- Typography and color tokens: `public_html/mcp-setup.html`, `mcp-docs.html`, `partners.html`, `colors_and_type.css`
- Header/footer: `public_html/assets/entia-nav.js`, `entia-footer.js`
- LLM icons: `public_html/assets/llm-logos.svg`

Nothing in this kit was invented. If an asset is referenced in code but the file does not exist on disk, it is listed in `MISSING.md`.

## Usage by Design

1. Read `07_GUIDE/BRANDING_GUIDE.md` first — tone, identity, do/don't.
2. Use `02_TYPOGRAPHY/typography.md` and `03_COLORS/colors.md` as the canonical token reference.
3. When designing landing variants, base them on `06_LANDING_STYLES/landing.css` patterns (`.client-card`, `.stats-bar`, `.try-section`, `.code-block`, `.badge-*`).
4. Use `01_LOGOS/USAGE.md` to know which logo variant goes where (nav vs trust seal vs favicon).
5. To bundle the kit for handoff: `bash 08_DOWNLOAD_BUNDLE.sh`.

## Conflict notice — two type/color systems exist in production

The codebase contains **two brand systems** today. Design must align them.

| System | Used in | Font | Color base |
|---|---|---|---|
| **A — Current (Inter)** | mcp-setup, mcp-docs, partners, funnel, index, MC dashboard | Inter + JetBrains Mono | `#3B82F6` |
| **B — Legacy (DM Sans)** | `colors_and_type.css` token file referenced from older landings | DM Sans + JetBrains Mono | `#3B82F6` |

CLAUDE.md (sec. 7, v19.1) states **Inter** is the official primary face. System A is canonical. System B is documented in `colors_and_type_legacy.css` for reference.

## Versioning

Kit version: `2026-04-29`. Re-run extraction after any change to:
- `public_html/assets/entia-nav.js`
- `public_html/assets/entia-footer.js`
- `public_html/colors_and_type.css`
- `public_html/mcp-setup.html` (used as canonical landing template)
