Brand guidelines
These guidelines describe how the ORIX identity is applied in ORIX Monitor. Each rule is tied to where it is implemented, so the document can be checked against the code: App/Sources/DesignSystem/Tokens.swift, Scripts/tools/make-icon.swift, Scripts/tools/dmg-background.swift, App/Sources/Features/MenuBar.swift, App/Sources/Features/SettingsView.swift and project.yml.
![]()
Identity
| Element | Value | Where it is defined |
|---|---|---|
| Product name | ORIX Monitor — "ORIX" in capitals, a space, "Monitor" capitalised | PRODUCT_NAME, INFOPLIST_KEY_CFBundleDisplayName in project.yml; window title; About tab |
| Tagline | Understand Every Pulse of Your Mac. | About tab (AboutSettings), DMG background |
| Family statement | "Part of the ORIX family of Apple utilities." | About tab |
| Bundle identifier | ai.spboucher.orix.monitor (family prefix ai.spboucher.orix) |
project.yml |
| Category | Utilities (public.app-category.utilities) |
project.yml |
| Copyright line | © 2026 Simon-Pierre Boucher | INFOPLIST_KEY_NSHumanReadableCopyright |
| Author / contact | Simon-Pierre Boucher — contact@spboucher.ai | File headers |
Naming rules
- Write ORIX Monitor in full on first mention and in every user-visible string that names the app. Never "Orix", "ORIX-Monitor" (except in file names), "OrixMonitor" or "the Monitor".
- File and artifact names use a hyphen and no space:
ORIX-Monitor-<version>.dmg,ORIX-Monitor-<kind>-<date>.pdf. - Internal identifiers use
ORIXMonitor(module, Xcode project, UI-test target) andORIXMonitorCore(package). TheORIXenum is the design-token namespace. - Command-line tools use lowercase with a hyphen:
orix-probe. - Launch arguments use the
-ORIXprefix (-ORIXSection,-ORIXDataDir, …).
The family and the product
The ORIX family shares a palette; each app has its own accent. In Tokens.swift the palette is documented as "The family palette, shared with the other ORIX apps", and the accent as "ORIX Monitor's accent pair: the cyan pulse over the family indigo".
| Layer | Colour | Light | Dark |
|---|---|---|---|
| Family | Indigo (accentSecondary) |
#5B5BF0 |
#8484FF |
| ORIX Monitor | Cyan (accent) |
#0B6E8A |
#22D3EE |
| Family neutrals | Deep navy canvas / cool grey text | see design system |
Rules:
- Cyan is ORIX Monitor's signature. It is the app tint, the pulse in the icon's glow, the arrow on the disk image, the accent rule in PDF reports.
- Indigo ties the app to the family. It appears as the second stop of the icon gradient and as the secondary accent in the interface (non-hardware page headers, bookmark markers).
- The neutrals are cool, never pure grey or pure black. The dark canvas is
#0A0D18, not#000000; the light canvas is#F4F5FA, not#FFFFFF. - Metric hues are functional, not brand colours. The eight family colours (CPU blue, GPU violet, memory green, …) identify subsystems. They are not used for branding surfaces, and they may be replaced wholesale by the colour-blind-safe palette.
- Status colours mean status only. Green, amber and red are reserved for success, warning and danger; they are never decorative.
The mark
The ORIX Monitor mark is the ORIX "O" crossed by a pulse: a ring, open at its left and right, with a heartbeat trace passing through the openings. It exists in two renditions that share the same geometry idea.
| Rendition | Where | Construction |
|---|---|---|
| App icon | Dock, Finder, About tab, disk image | Rounded dark plate; ring stroked with the cyan → indigo gradient; white pulse. See icon design |
| Menu bar glyph | Status item | 13 pt ring with a 1.6 pt stroke, cut by a horizontal band, crossed by a 1.5 pt pulse; drawn in black as a template image so macOS tints it for light, dark and highlighted menu bars (MenuBarRenderer) |
Rules for the mark:
- Do not recolour the app icon or place it on a different plate. The icon is generated by
Scripts/tools/make-icon.swift; change the generator, not the exported PNGs. - Do not add colour to the menu bar glyph. It must remain a template image.
- Keep the ring and the pulse together. Neither element is used alone as the app's logo. (The menu bar setting text refers to it as "the ORIX Monitor pulse icon".)
- Do not rotate, outline, or add effects (extra shadows, bevels, glows beyond the plate's built-in glow).
- Clear space. The icon plate already includes the standard macOS margin (an 824 px plate centred in a 1024 px canvas); do not crop it.
Typography
- The system font (San Francisco) everywhere — interface, PDF reports, disk-image background. No custom typeface is bundled.
- Rounded, semibold, monospaced digits for large readouts; small caps for card labels; monospaced for technical identifiers (API names, BSD device names, paths).
- Titles are bold; emphasis inside running text is avoided.
Voice
The tone of every user-visible sentence follows from the product's central promise: every number is traceable, and what cannot be measured is said to be unavailable.
| Principle | Example from the app |
|---|---|
| State the source. | "Device utilization reported by the graphics driver" |
| State the convention. | "100 % = every core busy" · "Per-process figures use 100 % = one core, as Activity Monitor does." |
| Say what is not available, and why. | "Not available through supported system interfaces." · "The network name is not shown: reading it requires Location Services, which ORIX Monitor never asks for." |
| Label estimates as estimates. | "This is a straight-line estimate, not a measurement." |
| Never alarm. | "One event alone does not indicate a hardware fault." · "Sustained load is normal during builds, exports or indexing." |
| Prefer the system's own vocabulary. | Nominal / Fair / Serious / Critical; App memory, Wired, Compressed, Cached files |
| Plain declarative sentences. | "History is only recorded while ORIX Monitor is running." |
Rules:
- No superlatives, no exclamation marks, no marketing adjectives in the interface.
- No emoji. Status is conveyed with SF Symbols and words.
- Commands follow macOS title-style capitalisation ("Add Bookmark", "Pause Sampling", "Erase All History…"); explanatory text uses sentence case.
- Use an ellipsis (…) on commands that open a dialog before acting.
- Use typographic quotes (“ ”) around names inserted in sentences, a space between a number and its unit ("2 s", "20 GB"), and "—" for a value that is unknown. Never print 0 for an unknown value.
- Privacy statements are factual and verifiable: "No account, no analytics, no advertising, no update check."
The quality words
These words have fixed meanings across the interface, the reports and the documentation, and must not be used loosely.
| Word | Meaning |
|---|---|
| Measured | Read directly from a documented system interface |
| Derived | Computed from measured counters (a rate, a ratio, a sum) |
| Estimate | A projection by the system or by ORIX Monitor; not a measurement |
| Best effort | Read through a public API from a property whose name Apple does not document; may be missing or change |
| Unavailable | No supported interface exposes it |
"Unavailable" is the state of a row rather than a quality of a value, but it is a case of the same MetricQuality enum and is shown with the same badge component.
Applications of the brand
| Surface | Treatment |
|---|---|
| Main window | canvas background, white or navy cards with hairline borders, cyan tint |
| Menu bar | Template glyph plus optional indicators (CPU, MEM, network, disk, battery) in the system menu-bar font weights |
| PDF reports | White page, ink #0E1222, cyan section rules, footer "ORIX Monitor · · <page>"; creator metadata "ORIX Monitor <version>"</td>
</tr>
<tr>
<td>Markdown reports</td>
<td>First line under the title: "ORIX Monitor <version> · Generated <date>"</td>
</tr>
<tr>
<td>Disk image</td>
<td>660 × 440 pt background: navy gradient (<code>#1D2440</code> → <code>#0A0D18</code>), cyan radial glow, cyan arrow, the product name, the tagline and "Drag ORIX Monitor to the Applications folder" (<code>Scripts/tools/dmg-background.swift</code>)</td>
</tr>
<tr>
<td>Exported file names</td>
<td><code>ORIX-Monitor-…</code> prefix</td>
</tr>
<tr>
<td>Notifications</td>
<td>Title "<Metric> is high" / "<Metric> is low"; body "Now <value>. Condition: <condition>." — no branding in the text</td>
</tr>
</tbody>
</table>
<h2 id="languages" tabindex="-1"><a class="heading-anchor" href="#languages" aria-hidden="true"><span class="anchor-icon" aria-hidden="true">#</span></a> Languages</h2>
<p>English is the source language. Canadian French (<code>fr-CA</code>) is the one translation, maintained in <code>Scripts/translations-fr-CA.json</code>. The product name and the tagline as rendered on the disk-image background are not translated; the About tab's tagline goes through the string catalogue like any other string.</p>
<h2 id="not-defined" tabindex="-1"><a class="heading-anchor" href="#not-defined" aria-hidden="true"><span class="anchor-icon" aria-hidden="true">#</span></a> Not defined</h2>
<p>The following are <strong>not</strong> specified anywhere in the repository and are therefore not part of these guidelines: a wordmark or logotype lock-up, a monochrome print version of the app icon, co-branding rules, a web or marketing colour system, and rules for the other ORIX apps beyond the shared palette and the bundle-identifier prefix.</p>
|