Typography
No typeface is approved for SOLMAMY’s brand identity yet. Until one is, every document in this project must say so honestly rather than picking one — this chapter exists to state exactly what’s real (the hierarchy structure) and exactly what’s missing (the actual typeface, sizes, and weights), not to fill the gap with an invented choice.
A typeface (Space Grotesk) is named elsewhere in this project, but it can’t be used here: it describes SOLMEME — the separate live crypto project/website at solme.me, not Sol Mamy’s own mascot brand (SOLMEME is a different entity from Sol Mamy — see Mascot Book, Brand/Mark Relationship) — so a typeface chosen for that other project’s site isn’t evidence of one for this brand.
One real exception: the wordmark already has a typographic rule
Section titled “One real exception: the wordmark already has a typographic rule”There is one piece of real, CANON typographic evidence — narrower than a general typeface, but genuine and citable. Sol Mamy’s own name-mark (“SOLMAMY”) has a dated, owner-confirmed rendering rule: always fused with no space, always two-toned (“SOL” in pink, “MAMY” in cyan — her clan and branch colors respectively, per Color System’s own tiered values), and always rendered on a single line, never wrapped or stacked. (Source: Story & Universe Book’s Lunaris Insignia System, “Wordmark typography rule — CANON” — cited here, not re-derived, per this project’s citation discipline.) This governs one specific mark, not general body/heading text — it doesn’t answer what typeface renders a paragraph of Brand Book prose, so the gap below is still real; it just isn’t a total absence of evidence the way the next section implies. (This also isn’t a real font/letterform to extract from: the wordmark is AI-generated character art, not rendered in an identifiable real typeface, so font-identification from it isn’t a viable extraction path either — same conclusion as pixel-sampling, different reason.)
Why the remaining gap is open, not blocked by a decision
Section titled “Why the remaining gap is open, not blocked by a decision”A real typeface choice will still, eventually, need the owner to approve something — that part is not in dispute; this is genuinely OWNER-DECISION REQUIRED. The distinction this section draws is narrower: for color, a decision wasn’t even needed to get real values, because the costume’s colors are physically visible in an approved reference photo and could be measured directly (see Color System). No equivalent shortcut exists for typography — there’s no photo to sample a typeface from, so unlike color, this can’t be resolved by doing the work now; it genuinely needs someone to choose or supply a typeface first. That’s the whole difference: color skipped the decision by finding a technical path around it; typography has no such path, so the decision is the only route, not an optional shortcut worth attempting first.
Hierarchy structure — a proposed starting framework, not a sourced fact
Section titled “Hierarchy structure — a proposed starting framework, not a sourced fact”The following five levels are a proposed structure — Display/Heading/Body/Caption/Label is a common industry convention (used across many type systems, not specific to any one brand), offered here as a reasonable starting framework to apply once a real typeface exists. It is not sourced to any SOLMAMY-specific decision, and it is not derived from V1’s SOLMEME material — it should be treated as AGENT-PROPOSED and confirmed or revised once a real typography decision happens, not assumed settled.
| Level | Role | Use for |
|---|---|---|
| Display | Largest, most prominent text on a page | A book’s own title, a hero statement — used sparingly, at most once per page |
| Heading | Section titles | Chapter and section headers, at the density this documentation already uses (e.g. this file’s own ##/### structure) |
| Body | Primary reading text | Rule explanations, prose paragraphs — the bulk of every chapter |
| Caption | Text attached to an image or example | Describing what a specimen or reference image shows, kept visually subordinate to the image itself |
| Label | Short, small, functional text | Table headers, tags, UI element names — never full sentences |
Not yet determined for any level: the actual typeface, fallback stack, exact size, weight, line-height, and letter-spacing. Filling these in without a real source would be exactly the kind of invented canonical fact this project’s own discipline forbids — and even the proposed level names above should be reconfirmed, not assumed, once a real decision happens.
- Do not invent a typeface, size, or weight to fill this gap — anywhere, in any document.
- Do not adopt
tokens.json’s or the V1 brief’s typography values for brand identity — both describe SOLMEME’s own site, not Sol Mamy’s brand (see Rule above). This is the same boundary already enforced for color. - Do not treat this documentation’s own current rendering (whatever font a markdown viewer happens to use) as an implicit brand choice — it isn’t one.
Application
Section titled “Application”Not applicable yet — application examples (web, print, presentation) require a real typeface to demonstrate; none exist. Once a typeface is sourced, this section should show the hierarchy above applied to at least one real context.
What would close this chapter
Section titled “What would close this chapter”A real, sourced typography decision — either an owner-provided specification or a formally adopted proposal — covering: primary/secondary typefaces, a fallback stack, weight scale, and sizes per hierarchy level above. Once that exists, real specimen images (per level, at real sizes) become possible and should be added — this is asset-production work, not a redesign of the hierarchy above.
No timeline is set for this — it stays open until a typeface is actually sourced, not scheduled for a specific date.
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.