One ramp, two ladders, one anchor, two curves.

Size, leading and the ratio between them are read back off the specimen above each line; the tracking is the rung’s own --letter-spacing, lifted from the stylesheet. Weight is the one column that is a convention rather than a token — design.md keeps weight at the call site on purpose, so there is nothing to measure and saying otherwise would be the lie this page exists to prevent. Base is 16px.

Measuring from the live stylesheet.

These neutrals resolve to 0 distinct hues. The system wants exactly one — a second hue is the “two different greys” defect returning.

The ink is the exception and is deliberately achromatic (C —): a tinted ramp under a tinted ink would double the cast. And the three surfaces are a real elevation ladder, not a card = background rule — a dense console needs the steps.

Only the renderings the product actually ships are measured. text-secondary would score 1.06:1 and light up a red failure — and nothing in the codebase writes it. Inventing a failing combination nobody uses costs a reader an investigation, which is worse than a gap.

krova · base-100

krova · base-200

krova-dark · base-100

krova-dark · base-200

The seams between the four lobes are knockouts, not white paint — they are transparent, and they take whatever surface is behind them. That is the whole reason one file serves both themes: on krova the seams read as the light surface, on krova-dark they read as the dark one, and the teal never changes. The four panels above are the same /logo.png, rendered four times, with nothing applied to it.

Krova Cloud

mark box

—

square, overflow-hidden

mark painted

—

letterboxed by object-contain

gap

—

box edge to wordmark

wordmark

—

Seven call sites, one component — components/brand-lockup.tsx, which resolves the artwork through the one LOGO_PATH constant in config/platform.ts. It exposes no size prop, so a call site cannot ask for a size of its own — which is the whole mechanism. It applies no filter, mask, tint or dark: variant either: the mark is drawn as authored on every surface in the product.

This was measured, not chosen. The console sidebar was made canonical and its rendering read out of a real browser — the numbers above are that reading, live, in whatever theme and viewport you are in. Before it, the seven sites shipped four icon sizes (48, 44, 36 and the sidebar’s 32), two type rungs and two weights, and app-shell.tsx disagreed with itself: its own mobile header drew a different lockup from its own sidebar.

Three things differ, deliberately, and none of them is a size. The console sidebar renders the unwrapped variant — the same mark and the same wordmark as bare siblings, because the collapsed rail hides every child after the first (components/ui/sidebar.tsx) and a wrapper would defeat that. The console’s mobile top bar renders markOnly: at 390 that row has 136.2px left for the brand and the lockup needs 156.6, so the wordmark gives way rather than the mark shrinking — the same rule the collapsed rail follows, and the drawer one tap away still carries the wordmark. And email cannot run React at all, so lib/email/format.ts turns the same constant into an absolute URL and the templates size it themselves — at 43 × 28 beside an identically-set wordmark (20/28, weight 700, tracking −0.2px), which is the one place the mark is drawn at a size the app does not use.

1. One component, seven call sites, and the email header.

   The landing, sign-in and onboarding layouts, the footer, the mobile drawer and both of the console shell's lockups all render one component, components/brand-lockup.tsx, which resolves the artwork through one exported constant, LOGO_PATH in config/platform.ts. lib/email/format.ts turns that same constant into the absolute URL every email header uses, because an inbox cannot run React. There is no second path to the artwork and, in the app, no second treatment of it.

2. The PNG is the mark. The SVG beside it is wired to nothing.

   public/logo.svg and public/favicon.png both ship, and neither is referenced by a single line of application code. If you are placing the Krova mark somewhere, take /logo.png — that is the file the product itself draws, and the table above is that file decoded.

3. It is never recoloured, and there is no dark variant.

   No call site applies a filter, a mask, a tint or a dark-variant class. The mark carries its own gradient, and its transparency — measured above — is what adapts it to a surface. That is why one file covers both themes instead of a light copy and a dark copy that drift.

4. It cannot be stretched, or resized at a call site.

   The one mark box is square and sets object-contain, and the artwork is 1.548 : 1, so it is letterboxed rather than stretched — the painted mark measures shorter than its box, which the panel above shows live. A call site cannot change that: brand-lockup.tsx exposes no size prop, so the box, the fit and the wordmark rung are not arguments anybody passes.

5. It always carries a text alternative.

   The alternative text is the brand name, and it is written once, inside brand-lockup.tsx — no call site can forget it because no call site supplies it. The repo's wider rule is the same shape: next/image types alt as required, and components/ui/image.tsx makes it required on the raw-img escape hatch too, so omitting it anywhere is a compile error rather than a lint warning somebody can suppress.

6. It appears without the wordmark in exactly two places.

   The collapsed console rail hides everything after a menu button's first child — see components/ui/sidebar.tsx — so it needs no prop to get there, and it is also why the sidebar renders the lockup's unwrapped form, as two siblings rather than one wrapped row. The console's mobile top bar reaches the same state with brand-lockup.tsx's markOnly prop, because at 390 that row leaves 136.2px for a lockup that needs 156.6. Both are the same rule: where the chrome cannot hold the wordmark, the wordmark drops rather than the mark shrinking.

7. The app icon is a different asset from the logo.

   Decoded, every square icon is the mark over a solid opaque plate; the wide logo is not. An icon has no surface to adapt to and has to supply one, which makes the icon set light-only by construction, and makes the two assets non-interchangeable rather than two sizes of the same thing.

8. Every declared icon size is the size the file actually is.

   app/layout.tsx and app/manifest.ts announce a size for each icon they declare. The table above sets those declarations beside the same files decoded through a canvas, so that row is a comparison rather than a restatement — and today every pair agrees.

• The minimum size.

  The mark now ships at exactly one size in the app — the 32px box measured above — plus the 16px favicon. Unifying the lockup removed the range without deciding anything: nothing enforces a floor, and no legibility test has been run at any size, so there is still no minimum to state here — only a smallest observed use, which is a different claim and must not be dressed up as the first.

• A clear-space ratio.

  The square icons reserve a transparent margin on all four sides, but the measured amount ranges across the set rather than holding one ratio, and it is proportionally largest on the smallest files. The wide logo reserves none at all. Inside the lockup the mark now has one fixed neighbour — the 8px gap measured above — but around the lockup, clear space is still whatever each of the seven layouts happens to give it, and whether it should instead be a fixed fraction of the mark's height is undecided.

• Rotation, cropping, monochrome, and using one lobe alone.

  The product does none of these anywhere, which is an observation and not a permission — and not a ban either. Nothing on this page should be read as licensing them or as forbidding them until somebody actually decides.

• Which file is the source of truth.

  logo.png is what renders, and logo.svg carries the same silhouette, but no build step derives either one from the other and nothing tests that they still match. Until one is made the source and the other regenerated from it, the two can drift apart without anything saying so.

• Whether the maskable icon should be a separate file.

  app/manifest.ts declares icon-512.png with both the any and the maskable purpose, so one artwork answers both. A maskable icon is cropped to whatever shape the host platform wants, and this one carries the same transparent margin as the rest of the set, measured above. Whether the maskable purpose needs its own full-bleed asset has not been looked at.

A brand page can state a minimum size, a clear-space ratio and a rotation rule in three sentences, and nothing in a codebase will ever contradict them. That is what makes them dangerous here: set in the same voice as the eight measured facts above, they would be indistinguishable from measurement. They are decisions the owner has not made, so they are shipped as questions.