Brand guidelines
How the ORIX family identity is applied in ORIX Sheet. The repository contains no family-wide brand book; the rules below are the ones that can be read from this project's sources, artwork generators and research notes. Where a rule is a convention observed in the code rather than a written decision, it is labelled as such.
Related: design system (tokens and components), icon design, localization, accessibility.
The family, as recorded in this repository
docs/research/technology-evaluation.md (environment audit) lists the sibling apps present on the
build machine: ORIX Scan, Calc, Audio (iOS), ORIX Monitor, Clean, Secure and Camera (in progress),
and states two facts that shape the brand work here:
- Each app ships its own design tokens. There is no shared runtime package.
- The shared palette is reused: navy canvas, cyan accent
#0891B2(light) /#22D3EE(dark), indigo secondary.
ORIX Sheet follows both: its tokens live in Packages/SheetUI/Sources/SheetUI/Design/Tokens.swift
and its icon uses the same navy plate and cyan-to-indigo gradient (see icon design).
This project did not inspect the sibling apps' sources; consistency with them rests on the palette
values quoted above, not on a side-by-side comparison.
Principles as applied here
| Principle | How it shows in ORIX Sheet | Where it is implemented or recorded |
|---|---|---|
| Local first | No account, no analytics; the About/Settings text says so and the copyright line reads "ORIX Sheet works entirely on this Mac." | App/Sources/AppSettings.swift, App/Sources/Welcome.swift, NSHumanReadableCopyright in App/Resources/Info.plist; verification of the network claim is in security.md |
| Honest about limits | Foreign formats are imported, never silently overwritten; exports show a report of what the format cannot hold | App/Sources/WorkbookDocument.swift, App/Sources/CompatibilityReport.swift; see persistence |
| No comparative claims | "No performance claim against a competitor is made anywhere in this project: we publish only our own measurements." | docs/research/competitive-analysis.md |
| Native, dense, calm | One toolbar and contextual inspectors instead of a ribbon; 4-pt spacing grid; one animation in the shared UI | WorkbookView.swift, Tokens.swift; see design system |
| Accessible by construction | Contrast of every token pair is a unit test; state is never carried by colour alone when the user asks for it | ContrastTests, ToolButton; see accessibility |
Source: the files named in the right-hand column.
Naming
- Product name: "ORIX Sheet" — two words, ORIX in capitals, a space, never "OrixSheet" or
"ORIX Sheets" in user-facing text. It is the value of
CFBundleName,CFBundleDisplayNameandPRODUCT_NAME. - Identifiers drop the space: module
ORIXSheet, bundle identifierai.spboucher.orix.sheet, document typeai.spboucher.orix.sheet.workbook, file extension.orixsheet, artifactsORIXSheet-<version>.dmg/.zip. - Document noun: "ORIX Sheet Workbook" (
CFBundleTypeName), "ORIX workbook" in running text ("classeur ORIX" in French). - Feature names found in the sources: Python Studio, Data Studio, Figure Studio, Model Auditor, ORIX Transform, ORIX Intelligence. The "ORIX" prefix is used for the two features that are engines of their own (Transform, Intelligence); the others are plain descriptive names.
- Names stay in English in every language. localization.md lists ORIX Sheet, Python Studio,
ORIX Transform and ORIX Intelligence as untranslated product names. Function names (
SUM,IF) also stay in English because formulas are stored in one locale-independent form. - Namespaces in code: design tokens under
ORIX.(ORIX.Palette,ORIX.Space, …); shared components carry the prefix only when the bare name would be too generic (ORIXCard).
Tagline
"Beyond Spreadsheets." appears in exactly one place: the DMG window background drawn by
design/dmg/make-background.swift (26 pt medium, cyan). It is not shown inside the application
(grep -r "Beyond Spreadsheets" over the Swift sources and string catalogs finds no other use on
2026-11-21). Treat it as packaging artwork; if it is ever used elsewhere it needs a French version,
which does not exist yet.
Tone of UI text
Conventions observed in the string catalogs (Scripts/translations/*.json, the English keys are
the source text):
- Say what happened and what it means for the user's file. Example (export preflight): "This format cannot hold everything in the workbook. Review what will change before exporting; your ORIX workbook is not modified."
- State guarantees in the indicative, without marketing adjectives. Example: "This workbook contains VBA macros. ORIX Sheet never runs macros; they are kept only if you export as .xlsm."
- Name menu paths with the ▸ separator: "File ▸ Export To".
- Sentence case for labels and menu titles;
SectionHeaderupper-cases its text at display time, so keys are written in normal case. - Undo names are short nouns or verbs ("Paste", "Bold", "Page Setup") because macOS prefixes them with "Undo"/"Annuler".
- French is Canadian French (
fr-CA) with Québec typography applied byScripts/localize.py: no-break space before « : » and inside guillemets, no space before « ; », « ? » and « ! », real ellipsis and apostrophes. Translators type ordinary spaces; the script fixes them. - Status over decoration: errors and "no result" messages are also posted as accessibility announcements, so the text has to stand on its own without colour or icon.
Known inconsistencies, recorded in localization.md and not hidden here: function summaries, formula parse errors and compatibility-issue texts are still English-only, because they come from packages outside the two localized catalogs.
Visual identity
- Colour: cyan accent on navy/near-white surfaces, indigo as the only secondary. Semantic colours (success, warning, danger) are reserved for state. Exact values and the measured contrast are in the design system.
- Gradient: the brand gradient cyan
#22D3EE→ blue#3B9BF5→ indigo#6366F1, drawn from top-left to bottom-right, exists only in the icon artwork (brand()indesign/icon/make-icons.swift). The application chrome uses flat token colours; no gradient token exists inTokens.swift. - Plate: the navy icon plate (
#1B2A4A→#0B0F1Ewith a soft teal glow) is shared by the icon and, in a wider form (#16233F→#0B0F1E), by the DMG background. - Typeface: the system font only. No custom typeface is bundled.
- Symbols: SF Symbols for all interface icons.
What to avoid
Each item is the negative of a rule that the code or the documents enforce:
- Using
accentas a text colour or under white text in light mode (fails 4.5:1; useaccentText/accentFill). - Carrying an on/off state by colour alone.
- Claims of superiority over another product, or numbers that were not measured in this repository.
- Words such as "cloud", "sync" or "account" in UI text: the features do not exist.
- Translating product or function names; hand-editing the generated
.xcstringscatalogs. - A second accent hue, decorative gradients in the chrome, or animations that do not go through
ORIX.Motion.respecting. - Hard-coded hex colours in feature panels instead of tokens. A count on 2026-11-21 finds one
Color(hex:)/Color(red:)literal acrossPackages/Feature*/Sources; chart series colours are a separate, documented palette (see chart engine).
Not defined anywhere in the repository
- A logo lock-up or wordmark other than the app icon and the text "ORIX Sheet" set in the system font.
- Rules for the icon on coloured backgrounds, minimum clear space, or monochrome variants.
- A written family brand book; licence or trademark statements for the ORIX name.