# ProofStamp Brand Guidelines v1.2

## 1. Brand idea

**The point that may matter later.**

Most moments do not need proof. Some do. ProofStamp marks the point worth preserving so a person or business can return to it later and verify what was recorded.

**Brand line:** **Add proof where it matters.**

## 2. Identity principles

The identity should feel:

- calm
- prepared
- verifiable
- private by design

Avoid crypto aesthetics, seals, shields, chain links, generic verification checkmarks and decorative complexity.

## 3. Primary wordmark

Canonical file: `assets/proofstamp-wordmark-blue.svg`

Approved construction:

- uppercase `PROOFSTAMP`
- master color `#162D52`
- small raised proof-point dot after the final `P`
- dot diameter = **0.22 × cap height**
- gap after final `P` = **0.30 × cap height**
- dot top approximately aligns with the cap top

The raised wordmark dot is not the same construction as the timeline or card marker.

Use the white wordmark on dark/navy fields and the black version only for monochrome production.

## 4. Color

| Role | Value |
| --- | --- |
| ProofStamp Blue | `#162D52` |
| Dark interaction | `#0E2344` |
| Main text | `#1B1F24` |
| Secondary text | `#66717E` |
| Borders | `#D8DEE6` |
| Light surface | `#F4F6F8` |
| Proof tint | `#E8EDF3` |
| White | `#FFFFFF` |

Functional states only:

| State | Value |
| --- | --- |
| Success | `#1F6B45` |
| Warning | `#8A5A00` |
| Error | `#A63A32` |

Functional colors are not brand colors.

## 5. Typography

### Primary

**Libre Franklin**

Recommended use:

- 400 Regular — body copy
- 500 Medium — navigation, controls and metadata
- 600 Semibold — headings
- 700 Bold — rare emphasis

### Technical

**IBM Plex Mono 400 / 500** for:

- SHA-256 hashes
- transaction IDs
- timestamps
- schema values
- code-like technical data

The logo remains fixed outlined artwork, not live text.

## 6. Proof point system

The proof point is a behavior, not a replacement for the wordmark.

### Timeline / graphic system

Canonical file: `assets/proof-point-timeline.svg`

The proof point is a **centered filled dot inside an outlined ring**. A navy segment crosses the timeline at that point while the rest stays neutral.

### Card / device marker

Canonical file: `assets/proof-point-card-marker.svg`

The marker is a white-filled ring with navy outline and a centered navy dot. The center dot is approximately 40% of the ring diameter.

Do not use a hollow ring alone as the standard card marker.

## 7. Imagery and composition

Show ordinary records and moments that may become important later:

- a photo before work
- an agreement or approval
- an inspection or handoff
- an AI conversation or decision record

The content stays primary. The proof point is a quiet secondary signal.

## 8. Voice

Plain English. Precise scope. Minimal hype.

Prefer:

- “Add proof where it matters.”
- “A record you can verify later.”
- “The point that may matter later.”
- “ProofStamp a file.”
- “Save the ProofStamp.”
- “Check a ProofStamp.”

Avoid presenting ProofStamp as magic, absolute truth, or a replacement for the original record.

## 9. Product language

### ProofStamp as a noun

A **ProofStamp** is the resulting verifiable record or receipt associated with a preserved digital state.

Examples:

- “Your ProofStamp is ready.”
- “Save the ProofStamp separately from the original file.”
- “Check this ProofStamp later.”

### ProofStamp as a verb

**ProofStamp** is also the branded action for creating a ProofStamp.

Examples:

- “ProofStamp a file.”
- “ProofStamp this photo before work starts.”
- “ProofStamp the record before you send it.”

Always capitalize **ProofStamp**, including when used as a verb.

Use the branded verb when describing the user action of creating a ProofStamp. Avoid awkward generic constructions such as “proof a file.” Use generic wording such as “add proof” when discussing the broader category or principle rather than the product action.

### Language hierarchy

- Brand idea: **The point that may matter later.**
- Brand line: **Add proof where it matters.**
- Product action: **ProofStamp a file.**
- Result: **Your ProofStamp is ready.**
- Verification: **Check a ProofStamp.**

This noun/verb convention applies across ProofStamp product surfaces unless a specific technical context requires more literal wording.

## 10. Plain-text signature

The canonical brand name remains **ProofStamp**.

Where the canonical visual wordmark cannot be carried, the approved human-facing plain-text signature is:

**ProofStamp͘**

Construction:

- `ProofStamp`
- immediately followed by `U+0358 COMBINING DOT ABOVE RIGHT`
- no intervening space

Use for:

- human-readable `.txt` ProofStamp receipts
- email receipt bodies
- copied plain-text receipts
- terminal-friendly human-readable output
- text-only profile or display contexts where the visual wordmark cannot be used

Do not use for:

- URLs or domains
- email subjects
- filenames
- JSON keys or machine-readable format values
- schema names
- package names
- transaction or attestation data
- commands, code identifiers or protocol identifiers

If correct Unicode rendering cannot be relied on, use **ProofStamp** without the combining point.

The plain-text signature carries the proof-point idea into text-only environments. It is not a replacement spelling of the brand and is not a live-text replacement for the canonical visual wordmark.

## 11. Do not

- redraw or approximate the wordmark
- change the master blue without a brand revision
- enlarge the raised wordmark dot for decoration
- use the wordmark dot as the card marker
- use the card marker in place of the logo
- use hollow-ring-only markers as the default on cards
- add crypto motifs to the identity
- write the brand name as “Proofstamp” or “proofstamp” in product copy
- use “proof a file” as the primary product action
- treat `ProofStamp͘` as the canonical spelling of the product
- use the plain-text signature in machine-readable identifiers