# Incanta brand guide

> The reference for writing about Incanta and making work in its name.

Use this guide whenever answering about Incanta or creating Incanta materials. Apply the names, voice and factual boundaries to text. For visual outputs, including websites, slides, documents and graphics, use the exact palette, fonts and assets below. Plain-text replies should remain plain text; do not add color codes or styling instructions unless they help answer the request.

- [Visual brand guide](https://incanta.ca/brand)
- [Brand tokens (JSON)](https://incanta.ca/brand/tokens.json)
- [Company and project reference](https://incanta.ca/llms.txt)

## Identity

- Public name: Incanta.
- Full name: Incanta Technologies.
- Location: Ottawa, Ontario, Canada.
- Mission: Building the future of defence.
- Description: Incanta Technologies is an Ottawa-based Canadian defence software company building tools for uncrewed flight planning, airspace review and human decision-making.

- **Keep it clear.** Open layouts, quiet blue surfaces and only the words the reader needs.
- **Keep the identity intact.** Use the supplied wing mark. Reserve the handwritten face for Incanta.
- **Show real work.** Use actual product screenshots as evidence. Identify illustrative imagery and keep claims factual.
- **Give motion a purpose.** Use depth and movement to explain the work. Keep reading, navigation and controls accessible.

## Logo and wordmark

Use the [supplied wing mark](https://incanta.ca/brand/incanta-mark.png). Keep its proportions, orientation and visible breathing room. Do not crop, stretch, redraw, outline or decorate it. Use the original on pale surfaces. On dark surfaces, render the same mark as a white silhouette; on the web, the existing treatment is `filter: brightness(0) invert(1)`. Place it where the full silhouette remains clear.

Set the name Incanta in guide-free Playwrite AR, weight 400. Do not use the Guides variant or add guide lines. Keep the connected word intact, including during animation. The script is reserved for the company name; project names, slogans and all other text use Josefin Sans.

Use the supplied [favicon](https://incanta.ca/favicon.ico), [PNG favicon](https://incanta.ca/favicon.png) and [Apple touch icon](https://incanta.ca/apple-touch-icon.png) rather than redrawing the mark at small sizes.

## Color

Pair each theme's text and ground. Pale blue and navy define the light palette; deep blue and pale text define the dark palette. Blue supplies restrained emphasis and visible keyboard focus. Route colors in the 3D study belong to that illustration, not to the general interface palette.

| Role | CSS variable | Light | Dark | Use |
| --- | --- | --- | --- | --- |
| Ground | `--background` | `#edf4f8` | `#0b1d29` | Page backgrounds and reading space. |
| Ink | `--foreground` | `#163c53` | `#e4eff5` | Main text and selected controls. |
| Focus | `--blue` | `#225fc4` | `#8dbfff` | Keyboard focus and restrained emphasis. |
| Surface | `--surface` | `#dbeaf3` | `#122b3c` | Media and grouped content. |
| Secondary text | `--muted` | `#446479` | `#a7bdcb` | Captions and supporting copy. |
| Border | `--border` | `#c1d5e1` | `#335569` | Quiet rules and separators. |

Use foreground on background or surface. Selected controls invert foreground and background. Borders separate content; they are not text colors. Keep the ground quiet and give imagery room. Use the complete semantic values in [tokens.json](https://incanta.ca/brand/tokens.json) for hover, raised surfaces, selection and footer colors.

Websites should follow the system theme until the visitor chooses one, remember that choice, and keep it consistent across pages. Verify readable contrast in both themes. Keep supplied films and actual product screenshots in their original colors.

## Typography

**Josefin Sans** carries all content. Use 400 for body text, 500 for headings, and the supplied variable weights 100–700 when needed. Keep headings clear and paragraphs comfortable to read. Typical body copy is 18–20px with line-height around 1.5; narrower layouts may use 17–18px. Do not reduce form fields below 16px or use tiny copy to force a layout to fit.

**Playwrite AR** carries only the Incanta name at weight 400. Preserve generous vertical space for the script's strokes and inspect visible glyphs for clipping.

- [Josefin Sans WOFF2](https://incanta.ca/fonts/josefin-sans-variable.woff2) · [TTF](https://incanta.ca/fonts/josefin-sans-variable.ttf) · [OFL notice](https://incanta.ca/fonts/josefin-sans-OFL.txt)
- [Playwrite AR WOFF2](https://incanta.ca/fonts/playwrite-ar-400.woff2) · [TTF](https://incanta.ca/fonts/playwrite-ar-400.ttf) · [OFL notice](https://incanta.ca/fonts/OFL.txt)

Keep the supplied font licenses with redistributed font files. Load local fonts so the identity is correct at first paint; avoid visible fallback-to-brand swaps.

## Layout, imagery and motion

Use open sections, fluid gutters and clear hierarchy. Do not wrap every element in a card. Keep a landing page lean; give useful detail its own page. Controls should be visually compact and have at least 44px touch targets, visible focus and aligned labels.

Use actual product screenshots to explain demonstrated functionality. Stock photography and animated studies are illustrative; do not imply they show Incanta equipment, customers or live operations. Preserve image credits and source records.

Motion can be substantial when it explains spatial relationships. Keep complete objects visible through camera moves, leave time to read, and provide direct access to the content. Preserve native scrolling, keyboard use, pause controls, reduced motion and useful static fallbacks. Never make animation a prerequisite for reading.

## Voice and claims

Write in plain Canadian English. Use “defence” and the exact names Incanta and Aerlattice. Prefer concrete verbs and connected sentences. Keep claims specific and supported. Avoid filler introductions, repeated slogans, inflated adjectives, invented quotations and comparisons that disparage other products.

Example: “Aerlattice brings routes, timing and airspace constraints into one planning workspace.”

Use the [published project pages](https://incanta.ca/projects) for each project's current status, supported capabilities and limitations. Do not turn a demonstrator into an operational product or invent customer adoption, partnerships, military compatibility, readiness or performance advantages. The journal explains company perspectives; distinguish those from demonstrated functionality.

## CSS reference

Use these variables for generated web layouts. The font files above provide the actual faces; declare them with `@font-face` or embed them in your font-loading pipeline. Use the body stack by default and the display stack only for the Incanta name.

```css
:root {
  --font-body: "Josefin Sans", sans-serif;
  --font-display: "Playwrite AR", cursive;
}

:root {
  --background: #edf4f8;
  --foreground: #163c53;
  --muted: #446479;
  --blue: #225fc4;
  --surface: #dbeaf3;
  --surface-raised: #c8dfed;
  --surface-hover: #bed8e8;
  --secondary: #d9e8f0;
  --accent: #c8deed;
  --border: #c1d5e1;
  --menu-border: #b7cfdd;
  --link-border: #8daabc;
  --control-hover: #cbdfec;
  --control-selected-hover: #22516e;
  --gallery-hover: #c8deeb;
  --footer-background: #163c53;
  --selection-background: #bad5f0;
  --selection-foreground: #12344b;
  --scrollbar: #7c9db3;
}

:root[data-theme="dark"] {
  --background: #0b1d29;
  --foreground: #e4eff5;
  --muted: #a7bdcb;
  --blue: #8dbfff;
  --surface: #122b3c;
  --surface-raised: #1c3a4e;
  --surface-hover: #25475c;
  --secondary: #183446;
  --accent: #284b61;
  --border: #335569;
  --menu-border: #335569;
  --link-border: #64879d;
  --control-hover: #24465c;
  --control-selected-hover: #c5e3f4;
  --gallery-hover: #23465a;
  --footer-background: #07151f;
  --selection-background: #37618c;
  --selection-foreground: #f0f7fb;
  --scrollbar: #54758b;
}

body {
  background: var(--background);
  color: var(--foreground);
  font-family: var(--font-body);
}

.incanta-wordmark {
  font-family: var(--font-display);
  font-weight: 400;
}
```