What it is
The identity Gravixar runs on: the mark, one accent color, a dark-only palette, a display and body pairing, and a mono label convention that shows up on every field, eyebrow and metric on the site. Not a deck describing a system. The system itself, in use, with the tokens that enforce it living in one theme block.
The coral is not the logo color, and that is the point
The mark carries a small solid square in pure red. Red at full saturation is a terrible interface accent: it fights everything near it, and it already means "error" everywhere else on a page. So the accent is coral at #ff6b35, chosen to sit beside that red rather than compete with it. Warm enough to read as the same family, calm enough to survive being on every link, hover state and label. The dark-ink wordmark variant shifts the square a little warmer for the same reason, so a printed lockup on white does not glare.
Dark only, and committed to
One surface at #0a0a0a, one text color at #fafafa, muted text at zinc-500, and hairlines in exactly two ranks: one for things that enclose, one for things that only separate inside an enclosure. There is no light theme, and not having one is a decision rather than a backlog item. A system that has to look right in both directions ends up with a palette that is a compromise in both. This one is tuned for a single condition and is sharper for it.
The type is where a generated brand gives itself away
Display is Hubot Sans, body is Mona Sans, both open variable grotesks, self-hosted. They were picked specifically because the obvious choices read as a default. A site set in Inter or the framework's own face announces that nobody chose anything, and for a studio selling design judgment that is the worst available first impression. Mono is Geist Mono, and it does exactly one job.
The mono field label
Small caps-height mono, 10px, uppercase, letter-spaced wide. It labels a section, a metric, a tool list, a date. It is the smallest element in the system and the one doing the most structural work, because it lets a page carry hierarchy without adding another heading size. Once a reader has seen three of them they know what one means, and after that the layout can be quiet.
Where to check it
Scroll. The type ranks, the coral, the hairlines and the mono labels on this page are the deliverable, which is a stronger check than any mockup of them would be. If a piece of the system were weak, you would be looking straight at it.
No client briefed this one, and I am not going to present it as though one did. It is my own brand, and the useful thing about that is the constraint it creates: I have to live inside these rules every time I ship a page here. That is a harder test than a guidelines PDF that gets opened twice and then ignored.
