SPB Git

Repository Public

brand-guidelines.md 15.2 KB

# ORIX DJ brand guidelines

These guidelines describe how ORIX DJ is named, described and drawn. They are derived from what the application already does: the strings in the interface code (App/Sources), the bundle metadata (App/Info.plist), the design tokens (App/Sources/DesignSystem/Tokens.swift), the icon generator (Scripts/icon.swift) and the disk-image background (Scripts/dmg-background.swift). Where a rule is a recommendation of this document rather than something enforced by code, it says so.

Related documents: design system, icon design, accessibility report, competitive analysis, distribution.

ORIX DJ icon

# 1. Name

Item Value Source
Product name ORIX DJ CFBundleDisplayName in App/Info.plist; window title in ORIXDJApp.swift
Tagline Mix the Music. Program the Experience. Scripts/dmg-background.swift
Automation language ORIX Script UTTypeDescription, Help menu, Docs section
Script file extension .orixdj UTExportedTypeDeclarations
Project file extension .orixdjproject (a package) UTExportedTypeDeclarations
Type identifiers ai.spboucher.orix.dj.script, ai.spboucher.orix.dj.project App/Info.plist
Copyright line © 2026 Simon-Pierre Boucher NSHumanReadableCopyright
Category Music (public.app-category.music) App/Info.plist

Writing the name:

  • "ORIX" is written in capitals, followed by a space and "DJ" in capitals: ORIX DJ. Not "Orix DJ", "OrixDJ", "ORIX-DJ" or "ORIXDJ" in prose. The unspaced form ORIXDJ is only an identifier (the Xcode target, the folder name, ORIXDJCore).
  • The name is not translated.
  • The language is ORIX Script, two words, both capitalised. Not "OrixScript" or "ORIX script".
  • The tagline is two sentences, each with a full stop, in title case as shown. It is used on the disk image under the name. It is not shown inside the application.

# 2. The ORIX family

ORIX DJ is one of a family of native Apple applications published by the same author under the ORIX name. The other members are ORIX Clean, ORIX Calc, ORIX Scan, ORIX Audio, ORIX Camera, ORIX Secure, ORIX Docs, ORIX Sheet, ORIX Monitor and ORIX Arcade. This document makes no statement about those applications beyond their names.

What the family shares, as far as ORIX DJ's own sources show:

  • The ORIX ring mark. The icon of each application is built on a ring, the letter O of ORIX. ORIX DJ draws its ring as a radial waveform; see icon design.
  • A common palette. Tokens.swift describes ORIX.Palette as "the family palette, shared with the other ORIX apps, with ORIX DJ's own accents". ORIX DJ's own accent pair is violet over the family cyan.
  • A naming pattern. "ORIX" followed by one plain word for what the application does.
  • A common home. The About tab of Settings links "ORIX apps" to orix.spboucher.ai and "Source repositories" to git.spboucher.ai.

When ORIX DJ is mentioned next to other family members, use the full name each time ("ORIX DJ and ORIX Audio"), not "DJ" alone.

# 3. Voice

The interface text of ORIX DJ is sober and precise. It states what a control does, in which units, and what it does not do. It does not promote. The following strings are taken from the code and set the standard:

Where Text
Limiter tooltip "Peak limiter on the master output (ceiling −1 dBFS, 5 ms look-ahead). It changes the sound when it works; the number below shows by how much."
Key readout tooltip "Estimated key (confidence N %). Estimates can be wrong; trust your ears." (N is the confidence the analyser reported for the track)
Emergency Stop tooltip "Stops every automation and bypasses every effect. Decks keep playing."
Auto DJ header "Deterministic and local: the order comes from the analysed tempo and key, and every transition is an ORIX Script you can read below. Auto DJ does not use Claude or the network."
Recording panel "Recording starts only from this button or its shortcut. It captures the master output as 32-bit float audio."
About, Privacy "All audio processing happens on this Mac. ORIX DJ needs no account and sends no audio anywhere."
Demo tracks notice "Demo tracks added. They are synthesised by ORIX DJ."
Grid tools (code comment made visible by the design) The beat grid is always adjustable by hand, because the analysis can be wrong.

Principles drawn from these:

  1. Say what happens, with the number. "Ceiling −1 dBFS, 5 ms look-ahead", "One turn is 1.8 seconds", "Full until the last 5 % of travel".
  2. State the limits. Estimates are called estimates. A feature that is local says so; the one feature that uses the network says so and names the destination.
  3. State the consequence of a destructive or audible action before it happens. "Decks keep playing." "Each one is an audible gap in the take."
  4. No hype. No superlatives, no exclamation marks, no claims about quality that have not been measured, no emoji.
  5. Second person, present tense, short sentences. Buttons are verbs or verb phrases in title case ("Import Music…", "Save Project As…", "Restore Previous Session"). An ellipsis marks a command that asks for more input.
  6. Units are written out properly. A space before % and before units ("50 % B", "48 kHz", "5 ms"), the true minus sign in prose ("−1 dBFS"), "BPM" in capitals.
  7. English spelling in the interface is British ("Colour-blind safe", "Favourites", "Analyse Again", "Normalise the peak"). Keep it consistent.

The same voice applies to documentation and release notes. Engineering documents report only measured numbers and say plainly what was not verified.

# 4. Feature names

Use the names below exactly as they appear in the interface. The first table is the section bar of the main window, in order (AppSection in App/Sources/App/AppModel.swift).

Tab title What it is Longer name used in text
Studio Decks on both sides of the mixer, with the library browser underneath "the DJ Studio" (source comment in StudioView.swift)
Library Tracks, crates, playlists, smart crates, history Library
Effects One effect rack per channel and one for the master "the effects rack"
Auto DJ Queue and automatic transitions Auto DJ
Automation Script editor, presets, visual builder, console, simulator, debugger Automation Studio
Docs The ORIX Script documentation reader "ORIX Script Documentation" (Help menu)
Claude Assistance for writing scripts, with the user's own Anthropic key Claude Studio
Record Recording of the master output, takes, trim and export Recording
MIDI Devices, monitor, mapping profiles, MIDI Learn MIDI
Perform Large waveforms and transport, triggers, safety controls "performance mode" (source comment)

Notes on the two "Studio" names: the tab is titled Automation and the feature is called Automation Studio in the code and documentation; the tab is titled Claude and the feature is called Claude Studio in every sentence of the interface ("Claude Studio needs your Anthropic API key", "The only network feature is Claude Studio"). Do not shorten "Claude Studio" to "the AI" in text; the Settings tab that configures it is titled AI.

Names inside the features:

Area Names
Deck layouts (DeckMode) Standard, Vinyl, Performance, Minimal
Deck count "2 Decks", "4 Decks"; menu items "Two Decks", "Four Decks"
Decks Deck A, Deck B, Deck C, Deck D (always a letter)
Deck controls CUE, SYNC, MSTR, KEY LOCK, QUANT, REV, BRAKE, TAP, BEAT HERE, BAR HERE, Loop IN / OUT, EXIT / RELOOP, Jump
Mixer Trim, High, Mid (Hi-Mid and Lo-Mid with four bands), Low, Filter, CUE, MASTER, Level, LIMIT, Cue Mix, Phones, Crossfader, Curve
Automation Studio modes (StudioMode) Editor, Presets, Visual Builder
Automation Studio panels (StudioTab) Console, Simulator, Debugger, Problems, Log, Monitor
Automation Studio side panes Script Explorer (toolbar: "Open (Script Explorer)"), Inspector
Automation commands Validate, Format, Run, Stop, Debug, Simulate, Emergency Stop
Triggers "Fire Trigger 1" to "Fire Trigger 8"
Library sources Crates, Playlists, Smart Crates, Favourites
MIDI MIDI Learn, "Learn New Mapping", profile, "Soft takeover"
Settings tabs (SettingsTab) Audio, Mixer, Library, Appearance, AI, Automation, About
Waveform palettes Spectrum, Ember, Colour-blind safe, Monochrome
Safety control Emergency Stop (always these two words)

Menus: Decks, Automation, View; the File menu contains New Automation, Open Project…, Save Project, Save Project As…, Import Music…; the Help menu contains ORIX Script Documentation.

Capitalisation: feature names are capitalised as above when they name the feature ("open the Visual Builder") and lower case when they describe an activity ("recording a mix"). Transport labels printed on controls are in capitals because they are control legends; in running text write "the Sync button", "key lock", "the cue point".

# 5. Colour

The brand colours are the design tokens; see the design system for every value and for the computed contrast ratios.

Role Light Dark Notes
Brand violet (accent) #6541E0 #9B7CFF The primary ORIX DJ colour
Family cyan (accentSecondary) #0B6E8A #22D3EE The secondary colour, shared with the family
Icon gradient #9B7CFF to #22D3EE Violet at the top left to cyan at the bottom right
Icon plate #1A2142 to #070A16 Vertical gradient, top to bottom
System accent (AccentColor asset) #7C5CFC same Standard controls, the icon glow, the disk-image glow
Ink on dark #F2F4FB Playhead and spindle of the icon, primary text in dark mode

Usage rules:

  • Violet and cyan together are the signature. Use the gradient only for the mark and for brand surfaces such as the disk image. Do not use the gradient on controls.
  • Dark is the home appearance. The application defaults to the dark theme, and the icon and the disk image are dark. Brand material should be shown on the dark canvas (#0A0D18) or the icon plate colours. On light backgrounds use the light values of the tokens, which are darker so that they remain legible.
  • Deck colours are functional, not brand colours. Cyan, orange, violet and green identify decks A to D and nothing else. Do not use orange or green as decoration, and never show a deck colour without its letter.
  • Status colours carry meaning. Green, amber and red (success, warning, danger) are reserved for level, warning and error or recording. Red in particular means recording, clipping or failure.
  • No colour-only meaning in any brand or interface material: pair colour with a word, a letter, a symbol or a shape.

# 6. Icon usage

The icon is produced by Scripts/icon.swift and described in icon design. Rules for using it:

  • Use the generated files: design/icon/orix-dj-icon-1024.png (master), docs/assets/icon.png (documentation copy) and the ten renditions in App/Resources/Assets.xcassets/AppIcon.appiconset. To change the icon, change the script and run it again; do not edit the PNG files by hand, because the script overwrites them.
  • The master is a 1024 x 1024 image with the 824 x 824 rounded plate centred and a transparent margin that holds the drop shadow. Do not crop the margin, add a second shadow, or place the plate on a tight coloured box.
  • Do not recolour the mark, rotate it (the playhead enters from the top), stretch it, or redraw the bars. Do not place text on the plate.
  • The ring mark without the plate is not provided as an asset. Inside the application the section bar uses the SF Symbol circle.circle.fill in the accent colour next to the name as a small stand-in for the ring; that is an interface element, not a logo, and should not be used in external material.
  • On documentation pages, reference the icon as docs/assets/icon.png at a width of 128 to 256 points.
  • Minimum size: the asset catalog includes a 16 x 16 rendition. At that size the mark reads as a ring with a centre dot, and the bars and playhead are not distinguishable; see the small-size notes in icon design.

# 7. Typography in brand material

The application uses the system font only (ORIX.Typeface): the rounded design for numeric readouts and for the name "ORIX DJ" in the section bar and the About tab (bold, rounded), and the standard design elsewhere. The disk-image background sets the name in the system font, bold, 26 pt, with the tagline in regular 13 pt at 60 % white. Brand material should follow the same choice: system font, bold for the name, regular for the tagline, no decorative typeface.

# 8. Do and do not

Do Do not
Write "ORIX DJ" and "ORIX Script" exactly Write "Orix", "OrixDJ", "ORIX script"
Describe features by what they do and with their measured figures Use superlatives or unmeasured claims ("studio quality", "zero latency", "professional-grade")
Say that key and tempo are estimates and that the grid can be corrected by hand Present analysis results as certain
Say that Claude Studio is optional, uses the user's own Anthropic API key, and that audio is never uploaded Suggest that ORIX DJ includes or resells an AI service, or imply endorsement by Anthropic
Say which hardware a statement was verified on Claim support for every controller or every audio interface
Use the interface names in section 4 Invent synonyms ("Script Lab", "AI Assistant", "Live mode")
Show the icon on dark or neutral backgrounds with its margin Recolour, crop, rotate or annotate the icon
Pair every colour signal with text, a letter or a symbol Rely on colour alone
Keep the tagline as two sentences with full stops Rephrase or translate the tagline in English material
Use British spelling in interface text Mix spellings within the interface

# 9. Third-party names

  • "Claude" and "Anthropic" are names of a third party. In ORIX DJ they appear only to tell the user where a request goes ("sent only to api.anthropic.com over HTTPS") and whose account is billed. Use them the same way in other material. See AI integration and the security report.
  • Names of other DJ applications appear only in the competitive analysis, never in the interface or in brand material.
  • The demo tracks are synthesised by ORIX DJ (the notice shown when they are installed says so). Brand material should use them, not commercial recordings, when a loaded deck has to be shown; this is a recommendation of this document.

# 10. Status of these guidelines

Sections 1, 4 and 5 describe what the code does on 2026-11-21. Sections 3, 6, 7 and 8 are editorial rules written for this document from the patterns found in the code; nothing in the build enforces them. The French-Canadian localisation declared in App/Info.plist did not exist as files at the time of writing (see the accessibility report), so there are no approved French forms of the feature names yet.

Files main
Menu

Theme