Bobby DB brand book

This is the official brand book for Bobby DB at brand version 1.0.0. It documents the approved Data Blocks identity and is generated from the same canonical source the product and the official asset files are built from, so the page, the assets and the PDF cannot drift apart.

Treat it as the working reference for anyone applying the identity. Where a rule here disagrees with a file elsewhere, the canonical source in the repository wins and the discrepancy is a defect to report.

Bobby DB is operated by Toros Ricos OÜ. The canonical future domain is bobbydb.com.

The product name is always written “Bobby DB” — two words, capital B, capital D, capital B. Never “BobbyDB”, “Bobby Db”, “bobbydb” in prose or “BOBBY DB” in body copy. The domain is written in lowercase.

Alexander van den Berg (alex@siteways.io) is the Product Owner and the sole final approver of brand decisions. Bobby DB Chat GPT Code Advisor is advisory only. Lovable is the implementation actor and holds no decision authority.

Environment scope: Working project and preview only. Publication authority: None — no production or publication authority granted.

On 27 August 2026, Alexander van den Berg selected Candidate 2 — Data Blocks from the three Phase 2 candidates. Exact supplied wording: “Data Blocks, that is the most nice one.”

Normalization (not a quotation): Alex selected the complete Data Blocks direction exactly as presented in Phase 2.

Not selected: Key Grid and Signal Vault. Both are preserved unaltered as historical decision evidence at /brand/candidates. Immutable record: docs/governance/brand/BOBBYDB-DATA-BLOCKS-PRODUCT-OWNER-SELECTION-2026-08-27.md

On 27 August 2026, Alexander van den Berg approved the implemented Data Blocks brand system and official assets as brand version 1.0.0. Exact supplied wording: “All designs approved; very nice.”

Normalization (not a quotation): Alex approves the implemented Data Blocks brand system and official assets as Bobby DB brand version 1.0.0.

This approval is additive: it is filed alongside the selection record, not in place of it. Immutable record: docs/governance/brand/BOBBYDB-BRAND-1.0.0-PRODUCT-OWNER-APPROVAL-2026-08-27.md

Brand version 1.0.0 is the approved state. The four approved colours, the symbol geometry, the wordmark outlines and the two typefaces are immutable at this version.

Any change to those values is a new brand version and requires a new, separately dated Product Owner record. Existing governance records are append-only: never edited, reworded or deleted. Additive, non-breaking documentation and new asset sizes ship without a version bump only when no approved value changes.

Every section of this book is labelled so a reader can tell a proven fact from a draft. The labels are applied to the brand book itself, not only to product claims.

Data Blocks expresses the product's central object directly: a stable key column with grouped values resolving from it. The composition implies a “B” without ever becoming a drawn letter, so the mark reads as structure first and initial second.

This is an INFERRED reading of the approved geometry, offered to keep future applications consistent. It is not a Product Owner-approved narrative and must not be quoted as one.

The symbol is built from 5 rounded rectangles inside a 48 x 48 viewBox. The coordinates below are the canonical construction; every official file is generated from them, so the mark is never re-traced by hand.

In the horizontal lockup the symbol's optical centre aligns to the wordmark cap-height centre; the gap is 14 symbol units. In the stacked lockup the symbol and wordmark share a common centre axis with a 12-unit gap.

The micro form is a responsive form of the same geometry, not a new logo: the two connector blocks are removed and nothing is redrawn, recoloured or substituted.

One-colour forms keep the 0.62 tone step on the lower value block and lower connector so the block structure survives without hue.

'Bobby' is always set in the surface foreground colour and 'DB' in the surface accent; in one-colour forms both words take the single colour. Never re-space, re-weight or re-set the wordmark — it ships as outlines.

The wordmark ships as baked outlines in src/lib/brand-wordmark-paths.ts, so no asset depends on a font being installed, downloaded or resolved at render time.

Two lockups are approved: horizontal for headers, toolbars and signatures; stacked for square and centred placements. Both have locked aspect ratios enforced by tests, so an asset cannot drift as it is resized.

Scale a lockup proportionally only. Never re-space the symbol against the wordmark, and never build a new lockup by placing the two primitives side by side yourself.

Clear space equals the width of the spine block (10 units of the 48-unit symbol, i.e. 20.8% of the mark width) on all four sides. The internal gaps between spine, connectors and value blocks are structural and must never be closed.

Symbol: 18px. Below 18px use the approved micro form (connectors dropped, same geometry). Horizontal lockup: 112px wide. Stacked lockup: 76px wide.

Full-colour on Quiet Lilac #F7F6FC, white, or Composition Ink #100D18 only. On photography or any other colour use the white or black one-colour form.

One-colour forms keep the 0.62 tone step on the lower value block and lower connector so the block structure survives without hue.

App icons keep the mark inside a centred 68% safe area of the canvas on a Composition Ink rounded square (22.5% corner radius). Social images keep all content inside a 6% margin.

App icon rasters bake #100D18 behind the mark and keep the four pixels outside the corner radius transparent by design, which is why the registry declares them transparent.

The social image is a single approved composition at 1200x630 with all content inside a 6% margin. It is fully opaque so no platform can composite an unintended background behind it.

Do not add campaign text to the approved composition. New social variants are generated from the builder, never edited in an image editor.

The favicon family uses the micro form at the smallest sizes so the block structure survives. The ICO packs the 16, 32 and 48 pixel rasters produced in the same run, so the ICO can never disagree with the PNGs beside it.

These four values were presented and approved as part of Data Blocks and are immutable at brand 1.0.0.

The approved four cannot carry a full interface alone, so the canonical source adds a documented set of surfaces, text colours and borders. These are derived tokens, not new brand colours, and they are marked as such in the source.

On light surfaces the accent is Block Violet #5B34D6 with #FFFFFF text on it. On Composition Ink the accent lifts to Secondary Violet #A98CFF so it survives the dark background. Group Aqua #35D8BE marks grouping and secondary structure in both schemes.

Violet carries state and emphasis, never large flat fills of body text. The soft tone step of 0.62 is reserved for the lower value block and its connector; it is not a general transparency for UI.

The ratios below are computed at render and build time from the same hex values the product uses, using the WCAG 2.1 relative-luminance formula. They are not transcribed from a design tool, and a regression fails the test suite.

Reduced motion is honoured throughout: brand block geometry never animates, and transitions collapse to zero duration under prefers-reduced-motion.

Both typefaces are self-hosted from /fonts with their licences shipped beside them. No brand surface loads a font from a third-party host, so rendering does not depend on an external service.

Use the named steps rather than arbitrary sizes. Display steps carry negative tracking; body and code steps carry none.

Keys, values and identifiers are set in Space Mono 400 on surface.light.raised / surface.dark.raised with a 6px radius; keys use text.*.primary and values use the accent only when they carry state.

Every key and value shown in brand material is synthetic and illustrative. Never place real, sample-from-production or scraped master data in a brand surface.

Spacing: 1 = 4px, 2 = 8px, 3 = 12px, 4 = 16px, 6 = 24px, 8 = 32px, 12 = 48px, 16 = 64px, 0.5 = 2px.

Radius: sm = 6px, md = 10px, lg = 14px, xl = 20px, pill = 999px, icon = 22.5%. Borders: 1px solid for structure, 2px solid for emphasis.

Elevation: sm 0 1px 2px rgba(16, 13, 24, 0.08); md 0 6px 18px -6px rgba(16, 13, 24, 0.24); lg 0 18px 48px -18px rgba(16, 13, 24, 0.38).

Focus: 2px solid #5B34D6 on light surfaces and 2px solid #A98CFF on dark, offset 2px. Focus is never removed.

Motion: 120ms and 200ms on cubic-bezier(0.2, 0.8, 0.2, 1). Under prefers-reduced-motion: reduce, transitions collapse to 0ms and no brand artwork animates. Block geometry never animates in any case.

Product icons sit on a 24px grid with a 1.75px stroke and square terminals, 2px corner radius — matching the block geometry

Icons are line forms; the brand symbol is the only solid-filled block artwork. Never build an icon out of the logo blocks.

Everything below follows from the canonical rules and the generated asset family.

These prohibitions were recorded with the Data Blocks selection and remain in force at brand 1.0.0.

The headline “Governed key-value data, ready for every product.” and its subcopy “Store, organize and publish stable collections. Use trusted public master data for free, or manage private collections through a simple API and MCP.” are PROPOSED drafts. The design approval of brand 1.0.0 did not convert them into approved commercial claims.

No customer, adoption, uptime, latency, certification, scale or SLA claim is approved or implied anywhere in this book. Trademark clearance and registrability are UNAVAILABLE: no check has been performed and none is claimed.

The official library holds 29 files under lowercase /images, enumerated in src/lib/brand-assets.ts and reproduced by `bun run brand:assets`. Every file is byte-reproducible from the builders: the manifest records size and SHA-256 for each one and the test suite re-derives them.

The PDF edition of this book is generated by `bun run brand:pdf` into /images/bobby-db-brand-book-1.0.0.pdf. No clock, no locale, no randomness and no network access: the PDF metadata dates are pinned to the approval date and repeated runs produce byte-identical output. The versioned file and the stable alias are written from the same bytes in one run.