Digital Surfaces

Canonical — Base rule (inherited, not new)

Per Brand Book — Logo & Mark, the mascot’s silhouette is the sole visual brand mark; no separate logo/wordmark exists. Every favicon variant below is a presentation of that same one mark — never a new, independent logo per site.

Resolved — Existing favicon assets

Two live favicon assets already exist, both raccoon-face icons (same mascot species): the main-site favicon (gold outline, chat-bubble prop) is owner-directed CANONICAL and stays current; the docs-site favicon (purple glow, holding a book) is legacy/unauthorized and off-canon-color, but its “book” motif independently confirms the First Ledger direction recommended below for the docs site — a future palette/motif update, not a current blocker.

Proposed — Favicon form

Of the candidate forms (cropped representation / simplified icon / brand icon / full mascot / separate UI mark), the base layer should be a simplified, cropped mascot-face icon — reasoning: Mascot Book — Reference Assets already establishes a real, sourced requirement that the design “must read correctly as a single-color silhouette at 16px, from a 10-foot viewing distance.” A favicon (typically rendered at 16–32px) is functionally the most extreme real-world test of that exact requirement — so the favicon should be the mascot’s face/mask silhouette (the highest-recognition, most compact part of her already-established silhouette), not a full-body reduction and not an unrelated “separate UI mark,” which would itself violate the existing “no separate logo” rule.

Current scope — community.solme.me and community.solme.me/docs/

The current scope is one site, community.solme.me, with its documentation living at community.solme.me/docs/. There is no second, separate app. or community. domain in current scope.

Shared brand DNA: per Brand Book — Logo & Mark, the mascot’s silhouette is the sole visual brand mark, with no separate logo/wordmark — this holds identically for the main site and its /docs/ surface, because a documentation subpath is still the same site, not a different brand. The base rule above (a simplified, cropped mascot-face silhouette as the favicon’s base layer, tested at 16px) applies to both surfaces unchanged.

Documentation-surface expression: within that shared base, /docs/ may carry a distinguishing accent consistent with its actual function — recording/reference — without inventing a new brand. If a Vault-artifact motif is wanted for that accent, the First Ledger (Story & Universe Book — the original manifest recording everything ever collected) is the best-reasoned candidate on file, since a documentation surface is a ledger, close to literally — but this is a design option, not a current, decided asset; no image exists.

Site UI color/typography: tokens.json, the site’s own UI/implementation color and typography values (buttons, backgrounds, layout), is historical/reference material from the site’s pre-rebuild design lineage — not a confirmed description of the current live implementation, and not something this Brand Book owns or verifies. See Color System — Site UI color/typography system for the full scope boundary.

Recommended — Open Graph (social preview) image

• Dimensions: 1200×630 (industry standard, so the asset renders correctly across Twitter/X, Discord, Telegram, and generic link-preview crawlers without per-platform variants).
• Mandatory mascot rule (follows directly from existing canon, not new): per Brand Book — Logo & Mark, no separate logo exists, so every OG image must show Sol Mamy’s mark — never a wordmark-only or logo-free treatment.
• Recommended template: a shared visual base (Sol Mamy + background treatment), with the optional /docs/-specific accent from the current-scope section above if one is ever produced — one system, not per-domain variants, since there is only one current site.
• Per-page-type variant, recommended: one shared OG template for the documentation site (title + book/chapter name overlaid on the shared base) rather than a bespoke image per article — matching how the docs site itself is structured (many chapters, one system).
• Genuinely left to production/design, not decided here: exact typography treatment, precise layout, and the actual asset file — this chapter specifies the requirement and logic, not the finished image.

Current — The brand recognition principle for community.solme.me and /docs/

How does a visitor know community.solme.me and community.solme.me/docs/ are the same brand, not two unrelated things? Shared DNA = the mascot-face base mark (Brand Book — Logo & Mark), present identically on both. No accent system is required to answer this — a documentation subpath of the same site is already the same brand by default; an artifact-based accent on /docs/ (the First Ledger candidate above) is an optional future refinement, not something needed to close this question.

Recommended — General meta/SEO requirements

Every page’s title tag should include “SOLMAMY” or the specific product name (Vault, Launchpad, docs) for recognizability in search results and browser tabs; meta descriptions follow each page’s own content (Brand Book does not template copy it doesn’t own). A dedicated SEO scoping pass remains a real, separate future task if more than this baseline is needed.

---

Part of the SOLMEME Brand Documentation System. Content status (Canonical/Proposed/Open/etc.) is this book’s own axis; ownership/rights are separate — see OWNERSHIP_AUTHORITY.md at the documentation system’s root.