Brand

Writing about Proof.

The mark, the wordmark, the name, the palette and the type, as shipped, with the files to download. Nothing on this page is aspirational. Every value is read from the live stylesheets, and the wordmark below is rendered by them.

press contact hello@reqproof.com share card 1200×630 retired marks in the museum

01 · The mark

The P and the dot.

The site’s favicon is the canonical mark, shown here at plate size. Use it as supplied; the SVG and the PNG renders are the same mark.

The Proof mark: the wordmark's P in pale phosphor on the tube's near-black, with the green period at the lower right.

The mark, from assets/brand/proof-mark.svg · identical to /favicon.svg

The wordmark’s own P — the glyph outline from the site’s Space Grotesk file at weight 600 — in the phosphor ink #D2FFE2 on the tube ground #050807, signed with the wordmark’s period. The dot’s color is authored in display-P3, color(display-p3 .144 1 .174), and falls back to #2BFF6F on standard displays; the PNG renders carry the sRGB fallback. Do not recolor it; it brings its own tile.

02 · The wordmark

Live text, not a logo file.

The wordmark is the header’s own render, scaled up. What sits on the plate below is not an image; the stylesheet that draws the header draws it.

Proof.

Rendered live by this page’s stylesheet · Space Grotesk 600, uppercase, letter-spacing 0

Space Grotesk at weight 600, set uppercase by the stylesheet with letter-spacing zero: PROOF. The letters take the phosphor ink #D2FFE2, the period takes the mark’s green — authored in display-P3, color(display-p3 .144 1 .174), falling back to #2BFF6F on standard displays; on the live header it is a tile authored for a 1000-nit target where HDR CSS and display support are available, with an SDR fallback — and the ground is the tube’s #050807. A raster wordmark was retired deliberately: a mark that is text cannot go stale.

03 · The name

How to write it.

Derived from how this site actually writes it, not from a naming policy.

In prose

Proof, one word, capital P. Every page title here reads … · Proof; every sentence says Proof.

One name, two things

Proof names the platform, which is the engine and the intent graph, and the named assurance practice, which runs audits and validates findings. Write Proof for both, and say which one you mean when the difference matters.

The footer line

Proof · founded and operated by Leonid Bugaev, the line the footer of every page carries. It names the person accountable for the platform and for the practice. The older wording, “a practice run by Leonid Bugaev”, is retired; it described the whole company as consulting.

Accountability

Write that a person validates every finding before it reaches you, or that a named reviewer validates each finding. Do not attach a signature to a finding; a signature would claim that one person authored the judgment. Names go on the promises, on the methodology bar, and on the published misses.

Set as the mark

The stylesheet renders the name uppercase, PROOF., with the period in the mark’s green. Written down, the name is still Proof.

ReqProof

The domain form. On this site it appears only inside domain and infrastructure names (reqproof.com, portal.reqproof.com, downloads.reqproof.com), never as the product’s name in a sentence. Write Proof unless you mean the domain.

04 · Boilerplate

Three lengths, and the attribution.

Quote one of these as it stands, or write your own sentence. One click selects a whole passage, and each label carries its real word count.

Short · 15 words

Proof reduces the work between a software change and the evidence required to trust it.

Standard · 27 words

Proof is AI-native software assurance for changes made by humans and coding agents. It keeps intent, dependencies, evidence, and history connected, so every change carries its proof.

Long · 55 words

Proof is AI-native software assurance for changes made by humans and coding agents. It keeps a living graph of software intent: requirements connected to their dependencies, code, evidence, hazards, and history. Every change carries its intent, blast radius, and evidence. The agent writes the change. Proof protects the agreement. The issue closes. The proof stays.

Attribution

Proof was founded by Leonid Bugaev and operates both the Proof platform and its named assurance practice.

Press contact: hello@reqproof.com. It reaches a person, not a queue.

05 · Color

Six values carry the site.

The chips are painted from the live tokens, so this page cannot disagree with the stylesheet it documents. One rule outranks taste: green always means machine state.

Ground #050807 The tube’s near-black glass (--paper). Every page sits on it.
Ink #D2FFE2 Pale phosphor (--ink). Every sentence, and the wordmark’s letters.
Affordance #FFFFFF The tube’s own light (--signal): links and buttons. White, so a control can never be mistaken for a verdict.
Verified green #2BFF6F Reserved (--pass). A check that ran and held — and the mark’s period, the one glyph that signs in this green off-state.
Amber #FFB000 Failure (--fail). A check that ran and broke reads amber on the tube.
Proof green #2BFF6F The dot in the mark and the wordmark’s period (--pq-green): authored in display-P3, color(display-p3 .144 1 .174); this hex is its standard-display fallback. On the live header it also carries a tile authored for a 1000-nit target where HDR CSS and display support are available, with an SDR fallback.

Green takes

The terminal prompt, active graph nodes, verification pulses, and the check marks in the register. Green reports what a machine did. The mark’s period is the one authored exception, and it brings its own tile.

Green never takes

Headlines, body copy, links, or buttons. A headline sets in the off-white inks — #D2FFE2, and #FFFFFF for the emphasised half — and an affordance takes the tube’s white light (#FFFFFF). Neither one reports a machine result.

Standing

This is the governing rule for every page, every theme, and every screenshot of the interface. Where a page still gives a headline the green treatment, that page has to change.

06 · Type

Two voices, no third.

Every piece of text on the site belongs to one of two layers.

Space Grotesk

The human layer: every sentence a visitor reads, and the wordmark. Variable, weights 300–700; the site speaks at 400 and 600.

IBM Plex Mono

The machine layer: labels, records, code, captions, and on this terminal theme the headings. Weights 400, 500 and 600.

07 · Do and don’t

Short, and meant.

Do

  • Use the files as supplied. The SVG and the PNGs are the same mark; pick by medium, not by taste.
  • Quote a boilerplate verbatim, or write your own sentence; anything between the two reads as ours without being ours.
  • Screenshot the real thing. The site and the portal are public; a live capture beats a reconstruction.

Don’t

  • Don’t recolor the mark. It ships with its own tube tile, the phosphor P and the green dot; on light grounds the tile does the work.
  • Don’t use green for a headline, a link or a button, in your own layout or in a screenshot of ours. Green reports machine state, and it is the one reserved word in this design system.
  • Don’t reach for the serif v7 mark. It is retired, and on display with every mark before it in the museum.
  • Don’t imply endorsement. A Proof mark near your product does not mean Proof audited it; only the public register says that.

08 · The share card

What a link unfurls.

When a page from this site is shared, this is the card it offers. Six pages carry their own: Product, Agents, Public proof, rsync, jsonparser and the Audit. The other pages share the default below.

The Proof share card: on a near-black ground, the PROOF. wordmark at the top left, the eyebrow ‘AI-native software assurance’, and the headline ‘Ship more changes without lowering the bar.’ set in phosphor-white terminal type behind a green prompt chevron, with a dim graph of requirements across the right half.
https://reqproof.com/assets/og/v10-card.png

The card carries both lines the homepage carries, in the same order: the category, AI-native software assurance, then the outcome, Ship more changes without lowering the bar. Green never lands on a word: it is the wordmark dot, the rule under it, the eyebrow bullet, the prompt, and the graph. The card is drawn from a template in the repository, so a headline change is a re-render and not a redraw. The Audit page keeps its own card, assets/og/v10-audit.png: the eyebrow is that page’s kicker, Continuous Correctness Audit, and the headline is the line reserved for that page, Find the bugs your tests missed.