Diamond StoneDiamond StoneAll plans

Diamond Stone Platform: Brand

Date: 2026-11-11. Revision 1. Status: draft for owner review. This document takes precedence over docs/DESIGN.md wherever they differ on logo, colour, typeface or wording.

Everything here was collected from work already done. Nothing is invented. Sources:

No document called "brand intel" or "brand intelligence" was found. The material above is what exists.

1. Logo

Copied into docs/brand/:

File Use
diamond-stone-wordmark.svg, -white, -black "diamond" over "stone" with the teal mark. Welcome screen, website header, documents
diamond-stone-wordmark-condensed.svg, -white, -black The short "dst" form. Narrow headers
diamond-stone-logomark.svg, -white, -black The mark alone
favicon.svg New, made from the mark: teal rounded tile, white mark. Browser tab
app-icon-maskable.svg New, made from the mark: full teal square, mark inside the safe area. Home-screen icon

The mark is a square with its top-left corner cut at 45 degrees. The idea recorded in the earlier design language: "Every stone is square; only Diamond Stone's is cut."

Where it appears in the app: the welcome screen (wordmark), the home-screen icon and browser tab (mark on teal), every notification (mark on teal), every document and PDF, and the website header. It does not appear inside working screens; the Halo and the content own that space.

Missing, to be made before release

  1. PNG icons at 192 and 512 pixels, an Apple touch icon, and the web app manifest with the theme colour. None exists anywhere yet.
  2. A clear-space and minimum-size rule. None is written down. Proposed: clear space equal to the mark's width on every side; wordmark never under 96 px wide; mark never under 16 px.
  3. An Arabic form of the name, and whether an Arabic wordmark is wanted.
  4. The exported logo files carry stray shapes outside the artboard; they should be cleaned by whoever holds the original artwork.

2. Colour

Name Value Use
Teal #008A8A The mark; large shapes; the app icon
Teal dark #006F73 Buttons, links, the Omnibar action. Used for anything carrying text, because white on #008A8A is only about 4:1
Teal soft #E6F4F2 Tinted backgrounds
Graphite #525862 The wordmark; secondary text
Graphite dark #343941 Main text

Status colours (done, waiting, attention) stay as set in docs/DESIGN.md section 5. Teal is the brand and the action colour, so "done" uses a clearly different green and is always paired with a tick.

Open: five slightly different teals exist across the earlier work (#008A8A, #008B8B, #007B7B, #00696B, #006F73). This plan uses the logo's own #008A8A and the brand file's #006F73 only. No dark-mode palette was ever defined; the one in the sketch is a proposal.

3. Typefaces

Owner's instruction of 24 September 2026 (earlier repository, document 80):

Typeface Use
Orbitron The wordmark only in the staff app; stone names on the website (as confirmed below). Never long text
Rajdhani Everything else: body, labels, buttons, tables, figures
IBM Plex Sans Arabic All Arabic. Latin letter-spacing is never applied to it
IBM Plex Mono Record numbers and codes

This replaces Inter and Instrument Serif in docs/DESIGN.md section 3. The sketch now uses these fonts.

Confirmed by the owner on 11 November 2026: Rajdhani stays for all text; a separate text face for small labels was offered and declined. Screen titles are set in Rajdhani bold; Orbitron is for the wordmark and the website's stone names.

A risk to test, not a reason to change: Rajdhani is narrow with a small body, so text set at the sizes chosen for Inter reads smaller. The sketch raises captions to 14 px, values to 16 px and titles to 19 px, and uses weight 500 for captions. It must be checked on the Galaxy A55 outdoors, with the accountant's long tables, and in the mixed English-Arabic screens, before the sizes are fixed.

4. Words

From the verbal identity (earlier repository, document 60):

5. What the buyer research means for the screens

From "Customers and Buyer Psychology" (July 2026):

Finding In the app and website
Never lead with price, "value" or "affordable" Stone pages lead with the photograph, origin and test data. No price badges, no "from OMR". A price appears only in a quote
Emotion shortlists; proof selects Picture first, then the technical sheet and certificates one tap away
Buyers fear the delivered stone will not match the sample One lot per job. The customer approves the range before accepting the quote; then, before loading, the layout of their own job (projects) or photographs of the actual pieces (small orders). Spare from the same lot is kept (docs/MATCHING.md)
Buyers fear late delivery The route line, the stage (dots in the staff app; a progress line with its stage in words in the portal) and a date on every order; a message on each real event
Buyers fear being blamed Downloadable test data, certificates and references on every stone
Origin is the opportunity: Omani stone, named An "Oman and the stone" page; origin shown on every stone and document
Supplier quarries are confidential The public and customers see "Oman" only; supplier names are visible to purchasing only

6. Stone names

Nine new names were proposed in July 2026 (for example Imperial Cream as "Calcis Velata", Sahara Beige as "Arenis Velata"). Trademark checks were preliminary only, and the earlier repository still uses the old names. Decision needed: which names the catalogue shows. The catalogue supports a main name and other names for each stone either way.

7. Motion

The durations and easing in docs/DESIGN.md section 11 stand. Two additions from the brand's film guide: Orbitron titles appear with a wipe, Rajdhani text with a short fade and rise; no bounce, shake or spin anywhere (one exception by the owner's decision of 11 November 2026: a single small overshoot, about 3 %, when a step is completed). No sound in the app.

This section is for the staff app only. The website and the client portal follow docs/SITE-MOTION.md: no wipes, mask reveals or overshoot there.

8. Where earlier decisions and this plan disagree

These were found while collecting the brand material. They need the owner's word.

# Earlier decision (September 2026) This plan (from this conversation)
1 Design language: square corners, hairlines, no glass, no blur, no cards Liquid Glass shell, rounded cards. The owner asked for this here in November, so it stands unless told otherwise
2 Diamond Stone holds no stock; it buys from Omani suppliers, inspects at their yards and ships from Sohar The plan has a yard, lots in stock, stock counts and stock valuation
3 A three-person company; seven roles Eight roles plus warehouse, drivers and own trucks
4 A supplier portal exists (requests, offers, orders, dispatch, invoices) No supplier portal in the first release
5 Export-first, to buyers abroad Local delivery by truck is treated as equally common
6 That repository is a working FastAPI and SvelteKit application with about 190 screens and a design lab A new build in Rust and SvelteKit in this repository

Row 6 matters most. The earlier repository is far more complete than the old demo in this one. Before any code is written the owner should say whether the new build replaces it, reuses its screens and documents, or continues it.

Claims the brand must not make (added 11 November 2026)

Research found no source for Omani marble in the Sultan Qaboos Grand Mosque, the Royal Opera House or the Sheikh Zayed Grand Mosque, none for ancient quarrying in Oman, and that much Omani "marble" is geologically crystalline limestone. The full list of what may be said, said only with a source, and never said is in docs/EDITORIAL.md section 6.

Names and origin (added 11 November 2026)

Three points from the catalogue research (docs/CATALOGUE.md section 6): the kind of rock is shown beside every stone name; a name containing a place the stone is not from is always shown with the true origin; and where a customer's paperwork needs the precise origin, it goes on that document while the public still sees "Oman".